It seems reasonable to me to enable indexing of the entire home folder, but disable indexing of file contents. Now I have to add/remove each new folder inside it, which is annoying. Also, I can add the entire home folder for indexing, but then my search settings look odd (it's not clear whether the home folder is indexed or not, see attached image) and I also get the following error:
kf.baloo: Failed to add exclude folder config entry for "/home/epopov/"
<img alt="194766253-31fc6a05-3af1-449f-9e51-0d31fce5530e.png" src="/fedora-kde/kde-settings/issue/raw/files/c1ac9328a472273e5ba1a96091e6bd9587320c95c298d3d796370cf1c68c2732-194766253-31fc6a05-3af1-449f-9e51-0d31fce5530e.png" />
This sounds like an upstream bug (add filters or something else). I don't think we should enable that by default in Fedora
Maybe upstream should enable indexing by default on Documents, Videos, Desktop, etc. folders only by default
Why not? I believe indexing without file content for the entire home directory is more efficient than indexing with file content for a few directories. I believe that indexing the entire home folder without file contents is more efficient than indexing only document-centric folders but with file contents. Indexing of the entire home folder is enabled by default in KDE neon and openSUSE Tumbleweed.
If you index the whole home directory, you'll also index non root container images, configs, etc. Until we have something really low priority and low impact, I don't think it's doable to enable by default. What we likely want is to index folders that matter instead of everything.
Baloo doesn't index hidden files and folder by default. It's also possible to exclude certain file types from being indexed (https://www.reddit.com/r/kde/comments/9ebbd5/baloo_disable_indexing_specific_file_types/).
As someone who does alot of development in my home directory, I do not like this idea. Whenever my entire home directory was being indexed, or re-indexed, it was very obvious because things slowed down. I'm also not sure about your setup. For me it is very easy to enable, or disable, indexing my entire home directory. Looking at your screenshot, I don't think if we enabled it by default, it would help you. Here is what the standard Fedora KDE install looks like.
<img alt="file-search-f36.png" src="/fedora-kde/kde-settings/issue/raw/files/35dd69a5e32d71453a81de846d6cd35d3a5d8e2f8fb0924528e526ad151391f6-file-search-f36.png" />
For me it is very easy to enable, or disable, indexing my entire home directory.
Can you try to enable it?
Interesting. On my RHEL 9 system I was able to enable my home directory (switched it to "Indexed") and it's running. In fact it's been running for over 30 minutes and it's almost at 50% done. On my F36 Kinoite I'm seeing something very similar to yours, with two entries. I didn't add the second entry, it just appeared. This seems like a bug to me. I'm going to test it on a couple other machines.
<img alt="file-search-f36-2.png" src="/fedora-kde/kde-settings/issue/raw/files/623ef919abd868f55bf6fff3fc187baf57d859dbf60e5e707945c70b274ff857-file-search-f36-2.png" />
I don't see this duplicate directory on Plasma 23. But I do see it on Plasma 24, 25, and 26.
FYI, here's when/where this was originally implemented, https://bugzilla.redhat.com/show_bug.cgi?id=1235026
There was an upstream one too I believe, I'll dig around for references
Bummer, I vaguely recall this may have not been tracked in any upstream bug, but did chat with upstream maintainers at the time, and we had agreed this would be an approach worth implementing. Looks like it never happened.
Log in to comment on this ticket.