the most essential programs are, of course, neofetch, pfetch, fastfetch, macchina, ufetch, and screenfetch.

For a filemanager try out nnn it takes a bit of getting used to but it’s very elegant and has a lot of clever little quality of life features. I use pulsemixer for volume and ncmpcpp + mpd for music. I like this cli calculator. It works basically as you’d expect and you can use . to mean “result of last calculation”.

I guess I’ll also plug my calendar program lol:

I wrote this calendar over the last few years. Pressing enter on a day allows you to write a note/journal entry for that day, which can be previewed quickly in the calendar. You can also add keywords like “appointment” which, if they exist in a note, will change the color used to display that day:

I’ve added various other features over the years like a help menu (press ?) and mouse support. There’s only a few minor things left I have planned so it’s mostly a “finished” project which is nice.

I work outta zsh as it’s the default for macOS but I can’t evangelize it much because I don’t have enough bash experience to differentiate the two. I think it’s pretty neat, though.

I use passion for my theme and spaceship for my prompt. Used to use powerlevel, but I found it to be too visually cluttered for my tastes after a while. With opsec stuff cleared out–here’s my neofetch:

and here’s an example prompt:

some useful aliases:

alias modx="chmod +x" # make file/script executable
alias calc="bc -e" # quick calculator
alias sl="ln -s" # symlink

I’d also recommend making a catch-all function for updating your package managers. I call mine shell-update and have it aliased to shu, which is the following function in my config:

brew update # homebrew sync
brew upgrade # update packages
brew cleanup # delete old versions

rustup update # rust toolchain update

npm update -g # node global update

pip3 list -o \  # python mass update
  | cut -f1 -d' ' \
  | tr " " "\n" \
  | awk '{if(NR>=3)print}' \
  | cut -d' ' -f1 \
  | xargs -n1 pip3 install -U

omz update # oh-my-zsh update

Your environment may vary.

ripgrep is an excellent grep replacement to check out. wild how much faster it runs. +1 on the eza (other poster said exa but that’s abandonware forked to eza)

check out deploy-rs and ragenix once you’ve replaced your current media server with a NixOS one. They make it much easier to apply configuration changes and to handle secrets if you need em for configs. +1 on start using flakes ASAP if you’re not already (pretty sure both these tools only work with flakes), Xe Iaso’s got a bunch of good blog posts about em if those are your jam.

I am currently playing around with it in a vm until the config is to my liking.

this is how I got NixOS to click for me, 10/10 highly recommend. even if it doesn’t stick this time keep your config in source control somewhere so you can revisit it.

Any reason to use an alternative to bash?

gonna strongly disagree with one of the other posters in here that you should use POSIX-compliant shells because they’re more portable, for a few reasons:

1. if you’re using the shell on a server or someone else’s workstation to do more than run a handful of diagnostic binaries you’re already wasting your time, and even then finding a quick one-liner in stack overflow to do some annoying repetitive task like filesystem cleanup or the like will be trivial. goes double for nixos where the likelihood you’re doing anything once shelled in besides editing a config or running a diagnostic becomes even more unlikely
2. speaking of, since you use nixos, you can trivially have your preferred shell environment available on any server you’re running for yourself
3. modern structured data pipeline-based shells (PowerShell, elvish, nushell, etc.) are far more ergonomic for both interactive and scripted usage

I wrote a little bit more about how modern structured data shells have been a more ergonomic option for like two decades now in a dunk tank post a few weeks back so I’ll just link that instead of elaborating.

even if you find you prefer flat text pipelines, zsh and fish are fine (and were preferable for me for interactive use before I started using pwsh and then elvish) and you’ll still wind up writing bash scripts anyway. or at least when I used those shells I don’t think I once wrote a script that targeted them instead of bash. also #! /usr/bin/env sh is fine, you should hopefully be well aware when you write scripts that have a chance of running on a system that has a weird shell symlinked to sh.

You can use fish or nushell if you really want to use something other than bash. Bash is useful because it’s installed in virtually all GNU/Linux machines by default. So unless you live in your terminal prompt 24/7 you dont need to change.

Zellij over tmux.

Best text editor is the one you like using and receives constant updates (and libre).

Make sure you start learning Nix Flakes as soon as possible if you want the most out of NixOS. The documentation is quite verbose so that’s what I’d prioritize.