Must have commandline tools?

fzf for quickly matching file names especially deep in the directory hierarchy

ripgrep for quickly searching for text content within files

dtrx for handling the right extractions of different archive types

xclip is incredibly useful to get and set data from the clipboard!

gopup is to html what jq is to JSON. It allows you to parse html to extract specific data for a given selector.

yt-dlp

ffmpeg

alsamixer

And on a more devops front k9s https://k9scli.io/

off the top of my head:

• vim
• git
• bash
• make
• whatever-compiler-im-using
• curl
• less
• grep

Ncdu is a really useful little utility that shows you what directories are using the most space on whichever drive/directory you select. Really useful little piece of software.

hdparm is another neato one that let's you test the read speeds of your drives, though it's more so something ya use once and forget exists.

Also, though Neovim is more popular, Helix deserves some recognition. It's a rust based, vim inspired text editor which removes the need to configure it, making it easier for people trying to get into terminal text editors.

Edit: Jerboa removed the first name, my bad.

• gcalcli : helps accessing google calendar using calendar api
• neix : rss reader
• I don't know if it counts but : fish shell

I mentioned this in another post, but tmux is awesome

I basically live in nvim. Being able to configure my editor in an actual programming language makes it so much more useful to me than vim could ever be.

I am thoroughly enjoying using mcfly.

Ranger and/or vifm as file managers. Can't live without them

I have mostly replaced all command line stuff with Emacs, but there are still a few CLI utilities that I continue to use, whether I am in the CLI directly or whether I am using Emacs:

• tmux or screen (terminal multiplexing)
• bash (shell scripting)
• grep, sed (filtering, formatting)
• ps, pgrep, pkill (process control)
• ls, find, du (filesystem search)
• ssh, nc, rsync, sshfs, sftp (remote access, file transfer)
• tee, dd (pipe control)
• less, emacs, diff, patch, pandoc (text editing)
• man, apropos (manual)
• tar, gzip, bzip2, xz (archiving)
• hexdump, base64, basenc, sha256sum (data encoding, checksums)
• wget, curl, (HTTP client)
• dpkg, apt-get, guix (package management)
• mpv (media player)
• ldd, objdump, readelf (inspecting binary files)
• zfs (maintaining my backup filesystem)

zoxide, makes file navigating so much easier.

btop is gorgeous ofc.

cheat, for cheat-sheets.

I really like entr - "Run arbitrary commands when files change"

http://eradman.com/entrproject/

argos-translate for offline machine language translation.

tmux & neovim for editing files and organizing the terminal displays.

asciinema for recording and playing back terminal sessions.

i use kibi as a text editor

i also have terminal client called alacritty

also doas instead of sudo

• ranger and mc - both are file managers, and their approach is so different that I choose one of them I need at the moment depending on what do I want to do (mc for traditional file management, ranger for looking around the directory tree and peeking into files)
• htop, tmux - classics
• weechat, profanity - for my IM needs
• ripgrep - for searching through files
• magic-wormhole for file and ssh public key exchange
• mosh for when the network conditions aren't ideal
• nmap to see if that machine I've connected into the network is up and what IP did it get
• bat for quick looking into files
• gdb, with mandatory gdb dashboard
• nvim for serious text and code editing, micro for more casual editing

I personally like bat, fd, rsync, btm, btop, rg, and nix. Nix is a package manager tho, so that's a whole bag of worms.

Kakoune (kak) has become my go to vim replacement. Keybinds are tweaked slightly to be more user friendly and more transparent about what it is you're doing.

I never mastered vim binding as well as I liked, but the more intuitive and better communicated binds for kak were easy to learn in comparison and I quickly swapped over.

bat is a nice one