Version: (using KDE 4.2.4) OS: Linux Installed from: Ubuntu Packages I see lots of minor bugs reported for kfind which could all be addressed together. Simply put, kfind does not work as a desktop search is expected to work, which is like this.. <Hit Shortcut, say Ctrl-F> <Type something> <Hit enter> Then your results come back. Simple. In kfind, not so. Firstly, desktop search needs to be QUICK. That I have to hit the Tab key four times to even begin typing something is a continual source of completely unnecessary annoyance. Sure, a tiny minority of people, including the developer, clearly, may need to begin elsewhere, but for the vast majority of users, it starts in the wrong place, every time, and there's no way to change it. And expecting users to enter regular expressions to get *any* meaningful results is frankly insane. Regexp and wildcards are powerful tools for advanced users, not default settings for a desktop search! Uber-functionality is great, so long as its built on something that by default, "just works", as expected. Or is development moving away from kfind towards integrating everything into Alt-F2 (Run dialog)?
The speed is due to the method used for searching. When strigi will be completely integrated, the speed will be increased. If you agree we can change the summary to: "set the focus to the 'named' field when kfind starts" Do you agree? (and maybe change the label "named" to something more intuitive)
AFAIK, KFind doesn't have a maintainer right now (I didn't had news nor messages from Eric); I just started to do some small fixes. - I agree on focusing the "Named" field on start. - Requiring regexps ? That is not mandatory nor needed. I don't even see the word regexp in the labels. So normal users will not have trouble with that. I agree, however, that the UI could be simplified and updated a bit. * Moving to Krunner or to use Strigi/Nepomuk ? No (that I'm aware of). I lack the time to work that much on this application. Sorry :-\ Regards
The speed of searching isn't an issue, that's nice and fast, at least on my hardware. The time-to-begin-doing-something is where the speed issue lies. In Windows 7, which I've briefly tested; there's even an option to begin searching if the user begins typing *anything* anywhere in an Explorer (like Dolphin) window. Now THAT is FAST searching. How long it takes for results to come back is secondary; I've already alt-tabbed to some other task. I'll be back. I'm glad y'all agree on where the focus should be at launch. I look forward to seeing/using that! As for the regexp/wildcards.. hrmph! On all my KDE systems, it's not possible to get back results unless you add some kind of wildcard character, e.g. "*". It's possible that's I've knocked something; I do have a tendency to copy preferences around; but I've spotted a few other bug reports on this site along the very same lines, and as far as I know, kfind *has* no preferences. Did we /all/ knock something? That too, may be possible, and if so, would it also be possible for kfind to enable reversion to a state where I can just type in the word "dog" and get results back for "dogfood.txt", "foodog.txt", "dog tales.doc", and "foobar.dog", as expected; or even just one of these files! Or just tell me how I fix my own broke settings! The label might be better called, "Find: " I hadn't thought too much about the overall GUI; so long as it does the job I don't mind too much, but yes; looking at it; it could be simplified, perhaps a very small, very neat default initial window, one input, one button, very like the Run Dialog. Extra functionality (and gui controls) could be expanded temporarily or permanently, as required; though most users probably never would. Change the name of this bug? I'm new to this bug reporting malarkey, so I don't know the implications of this move. Does that mean the wildcard issue is forgotten? Thanks for giving this attention! I wish I could help more with the code, but for now my time is also limited, and frankly, I haven't a clue where to start with the KDE collaborative development process; hopefully in the future.
*** Bug 209651 has been marked as a duplicate of this bug. ***
The initial focus was set to "Named" field in r1131315, as reported in bug 239026. (The name of that field cannot be changed now due to string freeze) IMHO this bug could be renamed, or even split (wildcard issue, simplify UI).
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!