Like, best text editor? Helix, Neovim, vim, emacs? All of the above, because why not? Currently leaning helix, becuase there's less setup involved with plugins and what not, but I'm not a serious programmer or anything.
Any reason to use an alternative to bash?
Any cool games? Best terminal file manager? Tmux or Zelij? Etc.
Useful aliases you use?
I'm currently messing around with NixOS, and was trying to build up a replacement for my current debian media server, and (eventually, hopefully, ) as a replacement to my current windows install.
I like debian a lot, but after installing it on both my laptop and server there was a lot of program drift between the two, when I wanted them to basically be identical, and then I found nix, and thought "this looks neat" and the idea of being able to reproduce everything on each install, with the same config format, appealed to me. I am currently playing around with it in a vm until the config is to my liking.
Seeing as the .nix config files are so portable I started working on a "module" for terminal apps to get about as close to a fully functional system as you can get with only a command line or terminal session, just to see what I could do.
So far I have quite a list, and looked over quite a few top 10 lists for this stuff, but was wondering if there was anything else out there I'm overlooking?
Pic is of my current bash prompt with starship, which was incredibly easy to get working and tweak thanks to home-manager modules. If anyone else is running starship and has a cool config they want to share, please do.
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.
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.
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:
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 tosh
.Thanks for the flake tutorial. I've implemented one already, but was a little confused about it. I plan to come back to it eventually.
I was planning to stick to bash, but since with nix you can switch between a few different shells trivially, I might as well look into the alternativces more closely.