https://bugs.kde.org/show_bug.cgi?id=433967
--- Comment #11 from tagwer...@innerjoin.org ---
Some ideas....
... the results in Comment 6 and Comment 7 don't make much sense to me when put
side by side
A plain and simple "baloosearch" doesn't mind where you are when you
call it, it should give you the same results.
If you want to filter results by directory, there is a "-d" option.
baloosearch -d Downloads adwaitrecolour
You can try
balooshow -x ~/adwaitrecolour"
and
balooshow -x ~/Downloads/adwaitrecolour
That will shows you what information baloo has for each file.
I'm guessing you might have loads of subdirectories and baloo can hit
a system limit. You can what the limit is with:
sysctl fs.inotify.max_user_watches
If this says 8192 and you've got more than about 8000 folders then
the indexing will go wrong. You can increase the limit following:
https://bugs.kde.org/show_bug.cgi?id=433204#c12
It may also make sense to purge the database and start again "clean"
balooctl purge
... For Comment 9
As above, a plain and simple "baloosearch" doesn't mind where you are
when you call it, it looks up its index. If you
cd /
baloosearch hosts
You'll just get hits just from the folders you've indexed. Assuming
you've got
folders[$e]=$HOME/
in your .config/baloofilerc then you are indexing your home folder
and below (and if not specified, that's also the default)
You can experiment with telling baloo to index "/" (without indexing
file content) but you'll very much need the increase in "max notify
watches"
... For comment 10
A search from "/" in Dolphin probably isn't using baloo
You can search from "/" is dolphin but it walks through the filesystem
looking for things that match - that can take a while (You'll see a
"searching" annotation in the bottom right of the dolphin window)
Hope I've got this right - and hope this makes sense!
--
You are receiving this mail because:
You are watching all bug changes.
