https://bugs.kde.org/show_bug.cgi?id=405094
--- Comment #4 from Ceaus <k...@pohw.nl> --- My apologies to Igor if I sounded as if was to assign blame. That is certainly not my intention. Although I understand your logic, it not a real defense against an improvement in this area: 1. Looking at the home page of Baloo, on the top of the architecture page it says: "Baloo is a metadata and search framework by KDE". The fact that meta is being mentioned is a give away that filenames should be supported to their maximum extent. Special characters not withstanding. 2. The 137K was a purely arbitrary number. I could also have said 5. The special characters should not be held hostage to support the argument of file content searches, or the problem of a list of results which is too long. 3. There is no mentioning at all, in any form, or in any MMI about the restrictions of the possible search parameters. If you cannot use certain characters, or the search string must be of a certain minimum size, than it should say so. You cannot confront the end-user with search results which are incorrect, for which no explanation is given. In my case I was finally able to understand the incorrect search results (that got me here in this bug report). But it could be much worse: the end user is confronted with incorrect search results, but s/he is unaware. Which can lead detrimental consequences on her/his part: Taking action because s/he thinks the document(s) do not exist. 4. It is extremely silly to integrate Baloo in the Dolphin file manager, making it indistinguishable from Dolphin, and then only partly support a typical task for a file manager: searching for files! Referring to a third party app (KFind) to search for files, to me is inexplicable. 5. The chosen technical solution (preferring an index over in-situ search) should not exceed the importance of a normal use case. If the size of the index becomes too big, then "we" have done something wrong on a technical level. That burden should not be put on the end user. 6. Now that I know that Baloo gives incorrect search result in certain circumstances, makes me question if and how I can "trust" Baloo in future times. Which undermines the whole purpose of its existence. How do I know I can trust Baloo? My real life use case: Last week I was called by my friend. She had to copy her home directory (XFS) to external hard drive (VFAT) for backup. That failed as VFAT does not support filenames containing ':' and '?'. My friend had about 25 of those files. As she does not have root access to the laptop, KFind was not an option for her to install. Over the phone we had to divert to a very complicated session trying to explain her how to use 'find' (command line) and how to rename the listed files. I would rather never, ever do that again. -- You are receiving this mail because: You are watching all bug changes.
