Shell Glob Pattern Tester

Shell Glob Pattern Tester

Test glob patterns against a list of file paths and see exactly which paths match — in real time, with semantics for Bash, Zsh, .gitignore, Python fnmatch, and Go path.Match. Type a pattern like src/**/*.{js,ts}, paste paths, and watch matches highlight green and non-matches fade out as you type.

Nutzung

1. Enter a glob pattern in the Glob Pattern field (for example **/*.log).
2. Wählen Sie einen Shell / Mode — the same pattern can match different sets of paths depending on whether you are in Bash, .gitignore, Python fnmatch, or Go.
3. Fügen Sie Ihre file paths one per line — or click a built-in example.
4. Matches highlight green with a check icon; non-matches stay grey. The summary shows the count and a note about the mode you picked.
5. Prefix your pattern with ! to invert the match (highlight everything that does nicht match).

Funktionen

• Five shell modes – Bash (with globstar), Zsh extended_glob, .gitignore, Python fnmatch, and Go path.Match, each with the correct semantics for *, **, ?, and brace expansion.
• Real-time highlighting – Paths re-evaluate as you type the pattern; no submit button.
• Brace expansion – {a,b,c} alternatives in Bash and Zsh modes, including nesting and cross-products like src/{js,ts}/**/*.{spec,test}.ts.
• Character classes – [abc], [!abc] negated classes, and ranges like [A-Z].
• Negation – Prefix any pattern with ! to flip the match.
• Mode notes – A short explanation appears under each result explaining how the chosen mode interprets the pattern.
• Quick examples – Load a web-project layout, a .gitignore-style log filter, or a docs/Readme example to learn by inspection.
• Nur clientseitig – Patterns and paths never leave your browser; works offline once loaded.

Häufige Anwendungsfälle

• Debugging .gitignore rules – Paste a list of paths from git status and see which would be ignored by a candidate rule.
• Writing build glob arguments – Validate that a pattern fed to tsc, esbuild, oder prettier --write matches the files you expect and nothing else.
• Authoring CI path filters – Confirm a paths: filter in GitHub Actions or GitLab CI hits the right subset of files before pushing.
• Translating shell scripts – Verify a pattern still works after porting code between Bash and a Python or Go service.
• Teaching glob semantics – Show students concretely why * does not cross directory boundaries in Bash but does in fnmatch.