ANGRYsearch VS cpu-control

I'm using ANGRYsearch for quick (index-based) searches. Works very well.

To the extend that ~8 years ago, when I switched to linux, I missed it so much I would not accept the searches linux had to offer. IMO not comparable with Everything... and actually went and learn python and pyqt just to fucking make somewhat similar alternative that would get me that instant results as I type results. Was actually surprised how little was needed to get it going... called it ANGRYsearch.

No clue about "Everything" but I use Angrysearch.

3) Search for any LibreOffice config files - in case any remain - and delete them. You could try using Nemo for that, but I recommend AngrySearch.

for Search I currently use AngrySearch. Which indexes your filesmanually triggered, and then searches that index when you type in the search box.

Angrysearch.

ANGRYsearch (very powerful file search)

Right now I'm using ANGRYsearch tied to a hotkey, which does the job very well, but it should actually be part of the DE because

Try Angry Search

cpufreq-utils in particular helped me micro-manage CPU clock speeds and max out battery life on my machine. By default, I limit my machine to work at 800 MHz (yup, that's only 0.8 GHz) for any low intensity tasks (idle, text editing, light browsing). When I need more power, I kick the CPU up a notch and throttle back to 800 MHz base speed as soon as the task is done. It sounds like a lot of gear-shifting, but I've tied my four different clock speeds to four similar key combinations, and now I'm so used to shifting gears I hardly notice I'm doing it on a daily basis. I've also written a wrapper script called cpu-control that handles any of the more complicated interactions with cpufreq-utils.

I've written a small bash script that facilitates use of cpufreq-utils a little. Makes changing CPU clock speeds a real breeze if you tie it to hotkeys.

You may want to manually throttle your CPU clock speeds so that badly-written software cannot send your CPU into overdrive and cause battery drain. I've written a little wrapper script for cpufreq-utils that you can find here. If used consistently (i.e. you always throttle your CPU clock speed down when doing light work and only crank it up when you've got heavier load to compute), it can prolong your battery life.

cpu-control bound to hotkeys (Ctrl + Alt + 1-4) to manually throttle CPU speeds and thereby conserve energy.

cpufreq-utils + cpu-control (allows you to throttle CPU clock speed to conserve energy)