https://bugs.kde.org/show_bug.cgi?id=477427
--- Comment #7 from tagwer...@innerjoin.org ---
(In reply to Firestar-Reimu from comment #5)
> I use this method to re-build the index dataset, and solved this problem.
That's good to know...
> Is there any file indexer which can index folders real time and not need
> hours to
> build a index dataset? I think Windows File Manager can do this.
If you are happy to search for just the filenames then you don't have to turn
on the "Content Indexing". It's the opening, reading, converting to text and
indexing each word of each of the files that takes the time.
You can follow the indexing as it is happening by running
balooctl monitor
and you can get a feel for how fast it is going. Baloo does "index in real
time" in that if you change a file, it notices and updates the index. It's just
that when you want to rebuild the index, it's a lot of work.
It looks as if you are indexing your Wine (maybe?) folders, that can include a
*load* of files. If you are indexing hidden files and folders, it probably
makes sense to exclude the .cache and .local/share/Trash
--
You are receiving this mail because:
You are watching all bug changes.
