Tag: Zsh

Zsh, the default shell on macOS: its errors, its options and the differences from bash that trip up commands and scripts.

Fixed: “export: not valid in this context” in zsh

zsh printing export: not valid in this context, and bash printing export: not a valid identifier, for a variable name with dots.

not valid in this context is zsh refusing a variable name with a dot in it. ASP.NET Core log categories are full of dots, so to turn one down through an environment variable, export won't do. env will.

0

Fixed: “zsh: no matches found” for a URL with a ? or a --include=*.cs Option

Two commands in zsh, each failing with zsh: no matches found, one naming --include=*.cs and one naming a URL with a question mark.

curl http://localhost:5190/demo/enum?status=placed and grep -rn 'class' src --include=*.cs both failed with zsh: no matches found, and neither program ever ran. Commands like these work in bash, and they appear that way in a lot of tutorials. In zsh, you have to quote them.

0

Fixed: “zsh: ===== not found” When a Word Starts with = in zsh

A zsh terminal where echo ====== prints zsh: ===== not found, and [ "$a" == 1 ] && echo same prints zsh: = not found.

I printed a line of equals signs in zsh, the default shell on macOS, and got zsh: ===== not found instead. The same thing happens to [ "$a" == 1 ], as zsh: = not found. zsh reads a word that starts with = as the name of a command; quote the word, and the line prints.

1

Up ↑