5 ms·
I find it funny that desktop search engines are not mentioned with a word here. This would be the first place to start when using Linux on a desktop (but of cou
by ktpsns 5y ago
I find it funny that desktop search engines are not mentioned with a word here. This would be the first place to start when using Linux on a desktop (but of course not a server, i.e. without any desktop environment).
These search engines are very powerful because they do deep file scanning, are based on mature frameworks such as Apache Lucene.
For KDE, this was called Nepomuk https://userbase.kde.org/Nepomuk https://userbase.kde.org/Nepomuk and is nowadays called Baloo https://community.kde.org/Baloo https://community.kde.org/Baloo, and can be used in fact from the command line (baloosearch)
For GNOME, this is (apparently, not using GNOME in the last years) called Tracker https://gitlab.gnome.org/GNOME/tracker https://gitlab.gnome.org/GNOME/tracker
- alex_smart 5y agoRecoll is also worth a shout-out. https://www.lesbonscomptes.com/recoll/ https://www.lesbonscomptes.com/recoll/
- srvmshr 5y agoI find the current Nautilus search to be very powerful, especially in searching inside texts & PDFs. It certainly does a far better job than Mac Spotlight or Windows Search. Under the hood, I am pretty certain it runs an extended command with regexes
- archeroed 5y agoI tried Plasma ( with i3 to replave kwin, didn't turned out to be a goo experience btw, back to bare i3) some times ago and directly deactivated this baloofile after seeing it was taking 1.7gb at boot ( maybe it was temporary ). I just use fzf when I don't know where something is.
- nitrogen 5y agoMy speedy system tanks when Baloo (and fstrim) tries to run after booting because everything runs at default priority. They really need to set nice and ionice on those processes by default. Thus locate is what I'll usually end up using.