i do not know if this counts as a command but you might want to check Atuin, what it does is help you find, manage and edit the commands you used in your shell history saves you a lot of time

The watch command is very useful, for those who don’t know, it starts an automated loop with a default of two seconds and executes whatever commands you place after it.

It allows you to actively monitor systems without having to manually re-run your command.

So for instance, if you wanted to see all storage block devices and monitor what a new storage device shows up as when you plug it in, you could do:

watch lsblk

And see in real time the drive mount. Technically not “real time” because the default refresh is 2 seconds, but you can specify shorter or longer intervals.

Obviously my example is kind of silly, but you can combine this with other commands or even whole bash scripts to do some cool stuff.

I’m a big enjoyer of pushd and popd

so if youre in a working dir and need to go work in a different dir, you can pushd ./, cd to the new dir and do your thing, then popd to go back to the old dir without typing in the path again

find /path/to/starting/dir -type f -regextype egrep -regex 'some[[:space:]]*regex[[:space:]]*(goes|here)' -exec mv {} /path/to/new/directory/ \;

I routinely have to find a bunch of files that match a particular pattern and then do something with those files, and as a result, find with -exec is one of my top commands.

If you’re someone who doesn’t know wtf that above command does, here’s a breakdown piece by piece:

• find - cli tool to find files based on lots of different parameters
• /path/to/starting/dir - the directory at which find will start looking for files recursively moving down the file tree
• -type f - specifies I only want find to find files.
• -regextype egrep - In this example I’m using regex to pattern match filenames, and this tells find what flavor of regex to use
• -regex 'regex.here' - The regex to be used to pattern match against the filenames
• -exec - exec is a way to redirect output in bash and use that output as a parameter in the subsequent command.
• mv {} /path/to/new/directory/ - mv is just an example, you can use almost any command here. The important bit is {}, which is the placeholder for the parameter coming from find, in this case, a full file path. So this would read when expanded, mv /full/path/of/file/that/matches/the/regex.file /path/to/new/directory/
• \; - This terminates the command. The semi-colon is the actual termination, but it must be escaped so that the current shell doesn’t see it and try to use it as a command separator.

Search for github repos of dotfiles and read through people’s shell profiles, aliases, and functions. You’ll learn a lot.

ps -ef | grep <process_name

Kill -9 proces id

I googled that -15 is better, I forgot what -9 even did, been using it for years.

Not a command but the tab key for auto complete. This made it much easier for me.

ctrl+r on bash will let you quickly search and execute previous commands by typing the first few characters usually.

it’s much more of a game changer than it first meets the eye.

I use $_ a lot, it allows you to use the last parameter of the previous command in your current command

mkdir something && cd $_

nano file
chmod +x $_

As a simple example.

If you want to create nested folders, you can do it in one go by adding -p to mkdir

mkdir -p bunch/of/nested/folders

Good explanation here:
https://koenwoortman.com/bash-mkdir-multiple-subdirectories/q

ripgrep

cd `pwd`

for when you want to stay in a dìr that gets deleted and recreated.

cat /proc/foo/exe > program
cat /proc/foo/fd/bar > file

to undelete still-running programs and files still opened in running programs

systemd-run lets you run a command under some limitations, ie

systemd-run --scope -p MemoryLimit=1000M -p CPUQuota=20% ./heavyduty.sh

nc is useful. For example: if you have a disk image downloaded on computer A but want to write it to an SD card on computer B, you can run something like

user@B: nc -l 1234 | pv > /dev/$sdcard

And

user@A: nc B.local 1234 < /path/to/image.img

(I may have syntax messed up–also don’t transfer sensitive information this way!)

Similarly, no need to store a compressed file if you’re going to uncompress it as soon as you download it—just pipe wget or curl to tar or xz or whatever.

I once burnt a CD of a Linux ISO by wgeting directly to cdrecord. It was actually kinda useful because it was on a laptop that was running out of HD space. Luckily the University Internet was fast and the CD was successfully burnt :)

parallel, easy multithreading right in the command line

inotifywait, for seeing what files are being accessed/modified

tail -F, for a live feed of a log file

Something that really improved my life was learn to properly use find, grep, xargs and sed. Besides that, there are these two little ‘hacks’ that are really handy at times…

1- find out which process is using some local port (i.e. the modern netstat replacement):

$ ss -ltnp 'sport = :<port-number>'

2- find out which process is consuming your bandwidth:

$ sudo nethogs