Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on programming.dev

4 replies

Gamma
programming.dev

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]'
4
txtsdreply
programming.dev

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.

2
Reptorian
programming.dev

Depends. I use G'MIC (Interpretative language for image processing largely inspired by bash) in CLI.

ig "C:\Users\User..."

If I need something with '$' in CLI, I'd be using $_path_rc\something_something. Sometimes with "" in case of spaces.

Other than that, I would be just running my own coded command in most case.

2

You reached the end

How do you shell expand your variables and why? | Spyke