How do you shell expand your variables and why?

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I’m sure there’s a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

Gamma@programming.dev · 1 year ago

Gamma@programming.dev · edit-2 1 year ago

I typically use find "$HOME/docs", but with a few caveats:

In Zsh or Fish, the quotes are unnecessary: find $HOME/docs
If I’m using anything potentially destructive: mv "${HOME:?}/bin" ...
Of course, if it’s followed by a valid identifier character, I’ll add braces: "${basename}_$num.txt"
I’m pretty inconsistent when globbing: "$HOME"/docs/* or "$HOME/docs/"* are common for me.
I don’t use "${HOME}" unless I actually need the braces. The reason? I write more Zsh than anything, and the braces are even less necessary in Zsh: $#array[3] actually gets the length of the third element of the array, rather than substituting the number of arguments, then the string 'array[3]'

txtsd@programming.dev · 1 year ago

I always brace my variables.

While I also use ZSH, I write most of my scripts in bash because they more often than not need to run on a CI/CD server.