Summary: | Can not find a part of a word in a filename | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Oleksii Zolotarevskyi <rockingcat> |
Component: | general | Assignee: | baloo-bugs-null |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | felix, nate, stefan.bruens, tagwerk19 |
Priority: | NOR | ||
Version: | 5.91.0 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Oleksii Zolotarevskyi
2022-04-14 22:09:37 UTC
Does `baloosearch xample` in a terminal window exhibit the same problem? (In reply to Nate Graham from comment #1) > Does `baloosearch xample` in a terminal window exhibit the same problem? Yes: $ baloosearch -d ~/Downloads xample Elapsed: 11,9903 msecs $ baloosearch -d ~/Downloads example /home/user/Downloads/text-example.txt Elapsed: 10,6788 msecs (In reply to Oleksii Zolotarevskyi from comment #0) > The problem does not happen when the File Search is disabled. In that case > searching for "xample" finds the file "text-example.txt". Checking on the current Neon Unstable - when Dolphin does a "filenamesearch" it finds results when searching for "xample" (happens for filename or content searches) However when Dolphin invokes "baloosearch", it gives results for "example" and "examp" but not "xample" ... Think this is a "Confirm" I've tried to get debug messages from baloosearch but I'm missing something (something obvious?) I've created a ~/.config/QtProject/qtlogging.ini file: [rules] *.debug=false kf.baloo.debug=true And I can see "indexing" entries when I look at: journalctl -f but I don't get anything extra when I try a baloosearch. What am I missing? *** Bug 453291 has been marked as a duplicate of this bug. *** Why does this bugzilla instance disallow any priorization, or categorizing? This is not a bug, but currently intentional (so close this as Resolved/Intentional?). But marking this as feature is not possible ... If you want baloo to find you "example" when you search for "xample", that's a feature request 8-) However, in dolphin, that you get a different behavour searching dependent on whether you have baloo enabled or not, or if you are searching from a folder indexed or not indexed by baloo, that is confusing. I'd flag that as a bug... (In reply to tagwerk19 from comment #7) > If you want baloo to find you "example" when you search for "xample", that's > a feature request 8-) > > However, in dolphin, that you get a different behavour searching dependent > on whether you have baloo enabled or not, or if you are searching from a > folder indexed or not indexed by baloo, that is confusing. But that is a bug in dolphin then. This bug has "frameworks-baloo" set as product. Even if baloo supported searching for something like "*.xample.*", it can not support searching for files not indexed. So dolphin should (optionally) crawl the filesystem (slow), after having queried baloo (fast, allows metadata/content match). (In reply to Stefan Brüns from comment #8) > ... So dolphin should (optionally) crawl the filesystem (slow), > after having queried baloo (fast, allows metadata/content match) ... Talking ideal behaviours? I think probably so. Dolphin should know what baloo has indexed, rely on baloo's results where it can, fall back to its own search when it cannot. Something that can give a "seamless" search if you are in your home folder in Fedora. It would be quite a project.... |