Version: (using KDE 4.1.2) Installed from: Debian testing/unstable Packages When I enter, for example, "ko" I see the suggestions Konqueror & Konquest in the completion menu. I don't see Kontact. When I enter "kw", I see nothing, not even KWalletManager. I am not sure what causes this, but it smells of deliberate if misguided design.
i'm surprised you see anyting for "ko" since the matching for .desktop registered applications doesn't start until 3 characters. in any case, the reason you won't see "kwalletmanager" would be because it isn't registered with the application database with it's .desktop file. probably has Hidden=true or is simply missing. as for not seeing kontact, it appears here just fine with "kon" (along with konqueror, konsquest, konsole, etc). if you aren't seeing kontact, that would be for the same reason you aren't seeing kwalletmanager. krunner does not currently keep a database in memory of all binaries on disk in your $PATH, so does not offer partial match suggestions for binaries unless they are either registered using a .desktop file or their full name is provided. "deliberate if misguided design" was that really necessary? honestly, i'd suggest looking at the code before commenting on design issues. really poor form. *** This bug has been marked as a duplicate of bug 162497 ***
After some more testing, "ko" does not always start the completion. Once you entered "konq" and press enter, krunner will remember this during the user session and start completion even if you merely enter "ko". That will, of course, filter out everything except Konqueror & Konquest. This does, of course, explain the failure to complete on "kw", as well. As to the "smells of deliberate if misguided design", I did not word that in a very good way. Yet, with the information available to me at the time, it appeared to be deliberate (and it is) and based on wrong decisions (as I said, due to the wrong info I gathered, I arrived at other conclusions). Please note that I did not say it _is_ "misguided design", I said it smelled of it, i.e. I suspected this might be the case. Turns out I was wrong. Really poor form? I don't think so. Bad choice of words (and the fact that I gathered false information)? Yes, definitely. Richard PS: It seems it's not possible to change the length of the string the Applications runner completes on, at the moment. Is this likely to change at some point?
Results with less than 3 chars should now be correctly taken care of in 4.2.2. The strange behaviour you described was due to a bug in handling autocompletion which has now been fixed -- J