in dolphin i ctrl+f to find a file in the current directory, kfind
pops up and can find nothing…
anyone else see this?
in case anyone wonders:
-it is not a case sensitive problem
-the system worked this way the first time i tried it, a few days
after initial install to a new drive
-clicked “Help” and read every word
-read the info in man kfind
-read the info in info kfind
-read the README in /usr/share/doc/packages/kfind
-read the three previous post found by the forum’s advanced search
-read google hits until my eyes watered, including all which
included “kfind” within the last year at kde.org
-used YaST to refresh kfind
-there are no updates waiting to be installed on this system
-searched bugzilla and its not there
-software specs in sig
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
Are you searching for the complete filename including the extension?
If not kfind isn’t able to find the file(s) you’re looking for.
This annoyance has been in KDE for a long time, even in KDE 3.x if I’m not mistaking.
Luckily the solution is simple, just add wildcards on both sides.
> Luckily the solution is simple, just add wildcards on both sides.
perfect! amazing…i wonder why that is not mentioned in any of the
help files, manuals, info, etc etc etc…
well, THANK you…and, i gave you a reputation boost!! thanks thanks
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
Is the English documentation really that incomplete? Because the German manual mentions the usage of wildcards (→without them, KFind will only look for exact matches - it’s not a bug, it’s a feature).
You could have used the forum search on that topic, because I have described that behaviour in →this thread (this thread is the first hit when typing ‘kfind’ in the searchbar - well, now it’s second. Just a hint).
Would someone be so kind to quote me? I think DenverD has still set me on “ignore”. Thank you.
Is the English documentation really that incomplete? Because the German manual mentions the usage of wildcards (→without them, KFind will only look for exact matches - it’s not a bug, it’s a feature).
You could have used the forum search on that topic, because I have described that behaviour in →this thread (this thread is the first hit when typing ‘kfind’ in the searchbar - well, now it’s second. Just a hint).
