Summary: | Please offer a whitelist instead of blacklist mode for file indexing | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | jm.ouwerkerk |
Component: | kcm_baloo | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | aspotashev, bugseforuns, hrvoje.senjan, ht990332, karl, kdejaeger, martin.cg.magnusson, nate, pieterkristensen, pinak.ahuja, plasma-bugs, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
jm.ouwerkerk
2015-09-09 16:06:25 UTC
As I mentioned in Bug 353193, the key here is to only index relevant folders (which makes searches return only relevant items) and allow the user to add additional folders. *** Bug 354838 has been marked as a duplicate of this bug. *** And then there is this problem: how to add a folder to the search and index of Baloo that is on an other partition? In this case a white-list option would be great! I also think a whitelist should preceed a blacklist. The current blacklist aswell as the new whitelist functionality should be editable in the kde 'file search' control module as well. Basic functionality IMO. After looking again, the whitelist is already there, isn't it? Basically the folders[$e]=/folder1,/folder2 Am I right? I'm using kde Neon at the moment. I read that they made a whitelist option but on my system it is still not there. I guess I have to be a little patient. The indexing code supports whitelisting, it's just not exposed in any UI (yet) *** Bug 386775 has been marked as a duplicate of this bug. *** The existing whitelist functionality is only for folders, as far as I can see. A related topic is also to whitelist file types. For example, baloo will not index text files with the extension .org (as explained here https://askubuntu.com/q/1130784/244753). It would be good if one could explicitly add file extensions to the list of files being indexed. *** Bug 333743 has been marked as a duplicate of this bug. *** I am using Neon KDE with plasma 5.19.4 and as far as I can see this bug is fixed. KDE became even more usable! Great! If I am not mistaking this bug could be marked as "fixed"... Indeed, this was implemented in 5.19! |