The article provides a command that shows the 10 most-frequently used terminal commands and the percentage of usages. I found it interesting, especially when I increased the count to the Top 25 (substitute -n10 with -n25) and commands that might be worthy of an alias or an AutoKey shortcut.

Here is mine. I cleared history earlier in the week and I do not think the results here are a true representative. An example of atypical usage is the flatpak entry. I only have three flatpaks installed (darktable, GIMP and krita), and I almost never use them.

I think flatpak usage is so high because this week I was playing around with flatpak command options, rather than actually running an actual flatpak. And when I do run a flatpak application I always run it from the terminal and I always run flatpak list first ... so the flatpak command gets used twice.

Also, ps and kill show up when I increased the count to 25, which makes sense. I use yelp to view man pages, and sometimes it does not exit properly.

The Reddit thread offers an additional command that shows the usage as a bar chart.

Interesting - I attempted a hefty git cherry-pick last week bringing my fork of Adapta up to date, and having been doing a lot of messing with xdotool and wmctrl attempting to make desktop mouse scrolling switch workspaces in Cinnamon,

For some reason the original filters out commands started from the current directory with "./" which seems not too useful but if someone insists: you can have awk does this itself as well by providing "^./" as a negative pattern:

That happened to me as well while testing, and in fact a bit over 1%. Upon noticing I decided to backup my ~/.bash_history so as to keep Heisenberg at bay -- and managed to fully delete the history when restoring, Hence the secondary system...

Note; that second one is the exact same save filtering out e.g. ./foo and ./bar same as the original does. Useful to a programmer I guess if constantly testing a just compiled ./foo but seemed to generally make too little sense to do as well. But yes, fun little thing.

That happened to me as well while testing, and in fact a bit over 1%. Upon noticing I decided to backup my ~/.bash_history so as to keep Heisenberg at bay -- and managed to fully delete the history when restoring, Hence the secondary system...

I had a corrupted ~.bash_history on one machine. It was not cat friendly & that just won't do, so fixed it by making a backup & then finding and removing the non-standard character, think a cat may have introduced this.

Backups are certainly essential when messing with this sort of stuff!

I'd be interested to find out how to filter out the display of the history result, which is affected by executing this, would help me to understand how this works .. will have to explore all this. I'm intrigued now.