You'll notice
Useful3 Signal0
Tricky bash double-bracket conditions are now treated as too complex instead of being misread.
What's wrong with this entry?
Anonymous. No account, no email.
What
The command parser now refuses to parse two [[ ]] shapes where zsh's cond-lexer disagrees with the parser, classifying them as too-complex differential cases instead.
Details
- a
[[ ]]pattern leaf containing&&now bails out, because zsh splits the word there - a pattern leaf containing a potential standalone
]]closer also bails out, because zsh closes the conditional differently - the
nodeTypefield was dropped from the unbalanced-parentheses result
Evidence
shell cond-lexer divergence (zsh splits the word there)
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.246
Shell function snapshots no longer round-trip through base64
Both mention bash
-
v2.1.246
Shell snapshot records shell options before functions
Both mention bash
-
v2.1.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash