Announced on the 9fans mailing list https://marc.info/?l=9fans&m=154827964823547&w=2

When hacking up Bash scripts, there are often things such as logging or command-line argument parsing that:
- You need every time
- Come with a number of pitfalls you want to avoid
- Keep you from your actual work
Here’s an attempt to bundle those things in a generalized way so that they are reusable as-is in most scripts.

We call it “BASH3 Boilerplate” or b3bp for short.
Found on https://willschenk.com/articles/2019/computer_setup_script/

While this blog article is about a new feature of the Scheme-based Guix Linux package manager, it contans the following interesting observation about erroneous shell settings: "it’s not uncommon for the shell to mess up with the whole environment. Why? Because, contrary to documented practice, it’s quite common for users to define or override environment variables in the startup files of non-login shells, ~/.bashrc for Bash, ~/.zshrc for Zsh. Instead, environment variable definitions should go to the startup file of login shells—~/.bash_profile, ~/.profile, or similar. But let’s face it: it’s a subtle distinction that few of us know or care about."

Executable Wiki: non-linear, text-based shell. I am not explaining this well, take a look at the screencasts.

Another unix shell emulation based on JavaScript, which includes command line completion, weather and location information and even an ssh client.

A simulated command-line interface to Google search functions.

Neat one-liner to find out which shell commands have been used a lot lately.