[chaliy]

Requested by Михайло · project thread

Stacked on #2563 (retargets to main when that merges).

What changed

Quoted or backslash-escaped glob characters are literal, as in bash:

• Words: a\*, a"*" and a'?' no longer glob.
• case and [[ == ]] patterns: "$x", 'a*', a\* and \[s\] match literally.
• Mixed words: "*"zz* with no match prints *zz* (the internal escapes used to leak). "$x"zz* reads $x, not $xzz.
• Single-quoted prefixes: 'a'$x expands and 'a'* globs. Both used to be literal.
• a{1,2}"*" still brace-expands.

Why

These are fidelity bugs from step 1 of the roadmap. A case or [[ ]] on a quoted variable that holds *, ? or [ took the wrong branch.

Before

$ cd /tmp/x && touch ab ac 'a*b' axb
$ echo a\* ; echo "*"zz* ; x='a*'; echo "$x"zz*
ab ac
\*zz*
a*b axb
$ case ab in "$x") echo glob;; *) echo literal;; esac
glob

After

a*
*zz*
a*zz*
literal

The new spec escaped-glob.test.sh (6 cases) matches real bash.

Risk

Medium, because it touches the lexer's word classification.

• The QuotedGlobWord convention (quoted glob characters backslash-escaped) now covers read_word and single-quoted words, with quote markers.
• expand_word unescapes for non-glob uses. Assignments and script analysis unescape literal parts.
• Known gap: data from an unquoted expansion in such a word loses \ before glob characters when nothing matches.
• Documented in knowledge/foundations/parser.md.

Checklist

• Failing spec first, compared with bash
• cargo test -p bashkit --lib, integration tests, clippy, fmt
• knowledge updated

https://claude.ai/code/session_019aFikmptPc91Fj4N2iDXQA

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bashkit	fd450e1	Commit Preview URL Branch Preview URL	Oct 07 2026, 02:57 PM