You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Substring matching breaks syntax highlight in ZED (which doesn't happen with VSCode nor GitHub Markdown).
Bash 5.2 enables substring matching by default (see patsub_replacement). This is particularly useful for injecting strings, but only when a $variable is present. In this example --volume=/tmp/mnt:/mnt wont be printed unless item in export MOUNTS is uncommented:
which doesn't happen with VSCode nor GitHub Markdown
They use different approaches to highlights, and whatever tree-sitter grammar in Zed is used, it seems to have issues with it.
It seems that this report should go to https://github.com/tree-sitter/tree-sitter-bash and not here.
Check for existing issues
Describe the bug / provide steps to reproduce it
Substring matching breaks syntax highlight in ZED (which doesn't happen with VSCode nor GitHub Markdown).
Bash 5.2 enables substring matching by default (see patsub_replacement). This is particularly useful for injecting strings, but only when a $variable is present. In this example
--volume=/tmp/mnt:/mnt
wont be printed unless item inexport MOUNTS
is uncommented:Reproducible example:
Environment
Zed: v0.159.7 (Zed)
OS: Arch Linux Wayland
Memory: 62.6 GiB
Architecture: x86_64
GPU: AMD Radeon RX 7900 XT (RADV NAVI31) || radv || Mesa 24.1.3-arch1.1
If applicable, add mockups / screenshots to help explain present your vision of the feature
ZED without any extensions:
OK
BROKEN
For reference, I've also tried installing d1y/bash.zed (extensions/basher) & rburmorrison/shell.zed (extensions/shell) but either behaves identically as ZED with no extensions
The text was updated successfully, but these errors were encountered: