Skip to main content

Showing archive results for November 2026

Posts

0 comments 0 reactions

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

Jagdish Kumawat

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.

  • Issues
  • Operating Systems
  • Mac
0 comments 0 reactions

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

Jagdish Kumawat

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.

  • Issues
  • Operating Systems
  • Mac
0 comments 0 reactions

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

Jagdish Kumawat

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.

  • Issues
  • Operating Systems
  • Mac
0 comments 0 reactions

Fixed: Adaptive Cards Designer Changes the Card Version to 1.6

Jagdish Kumawat

The Adaptive Cards Designer always writes version 1.6 into the JSON it copies and exports, even after you type 1.5. Teams and Copilot Chat support 1.5, so change the version in your copy.

  • Issues
  • Microsoft 365
  • Microsoft Teams