mirror of
https://github.com/zsh-users/zsh-syntax-highlighting.git
synced 2025-04-17 11:35:32 +08:00
![]() They fail as follows: ZSH_PATCHLEVEL=debian/5.7.1-1 Running test brackets Running test main # parameter-value-contains-command-position1 1..2 not ok 1 - [1,7] «$foobar» - expected (1 7 "assign"), observed (1 7 "unknown-token"). ok 2 - cardinality check # parameter-value-contains-command-position2 1..2 not ok 1 - [1,2] «$y» - expected (1 2 "assign"), observed (1 2 "unknown-token"). ok 2 - cardinality check (The "unknown-token" was printed by the `_zsh_highlight_main_add_region_highlight` call on line 967, after the loop.) Before the parent commit, they behaved as follows (note the "BUG:" and "Bail out!" on the first one — that's issue #670.2): ZSH_PATCHLEVEL=debian/5.7.1-1 # parameter-value-contains-command-position1 1..2 ok 1 - [1,7] «$foobar» - # TODO "issue #670" not ok 2 - have 1 expectations and 6 region_highlight entries: «expected_region_highlight=( '1 7 assign "issue ♯670"' )» «region_highlight=( '0 7 assign' '2 7 default' '2 7 command-substitution-unquoted' zsh-syntax-highlighting: BUG: _zsh_highlight_highlighter_main_paint: start(2) >= end(2) Bail out! On './highlighters/main/test-data/parameter-value-contains-command-position2.zsh': output on stderr # parameter-value-contains-command-position2 1..2 ok 1 - [1,2] «$y» - # TODO "issue #670" ok 2 - cardinality check |
||
---|---|---|
.. | ||
brackets | ||
cursor | ||
line | ||
main | ||
pattern | ||
regexp | ||
root | ||
README.md |
zsh-syntax-highlighting / highlighters
Navigate into the individual highlighters' documentation to see
what styles ($ZSH_HIGHLIGHT_STYLES
keys) each highlighter defines.
Refer to the documentation on highlighters for further information.