Shell command parsing catches more cases of mismatched quotes around bracket tests.
What's wrong with this entry?
The heuristic that flags shell input where a quoted operand contains ]] catches more shapes of the same problem.
- Bracket-test constructs are now scanned for
]]closers even when no separator follows. - Plain
testcommands get their own distinct reason string. - Commands that trip the check are marked as differential too-complex results.
possible parser quote-state desync
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash tool
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention bash tool
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention bash tool