diff options
| author | zeertzjq <zeertzjq@outlook.com> | 2026-07-27 06:29:58 +0800 |
|---|---|---|
| committer | zeertzjq <zeertzjq@outlook.com> | 2026-07-27 06:31:40 +0800 |
| commit | 1d36cf1dbed58db9ae72367eef07b5698584bcd5 (patch) | |
| tree | 4310cd2777d7948e1c687688c4eb5c2322f00146 /runtime/syntax/python.vim | |
| parent | ef93e939586300d7cd348724d16f3c507a4f13fa (diff) | |
| download | rneovim-1d36cf1dbed58db9ae72367eef07b5698584bcd5.tar.gz rneovim-1d36cf1dbed58db9ae72367eef07b5698584bcd5.tar.bz2 rneovim-1d36cf1dbed58db9ae72367eef07b5698584bcd5.zip | |
vim-patch:f88e719: runtime(python): Fix indenting for brackets within python byte strings
Problem: s:SearchBracket()'s skip-expression matches syntax group
names ending in "Comment", "Todo", or "String" to decide
whether a candidate bracket is inside a string/comment
and should be skipped for indentation purposes. Byte and
raw-byte string literals (b"...", rb"...") are highlighted
via the pythonBytes/pythonRawBytes syntax groups, which
don't end in "String", so brackets inside them (e.g.
b"[") were never skipped and were counted as real,
unmatched brackets, producing incorrect indentation.
Solution: Add "Bytes" to the indent script's existing suffix match,
so pythonBytes/pythonRawBytes are recognized directly, the
same way pythonString/pythonFString/pythonRawString
already are.
This supersedes an earlier version of this fix that
renamed pythonBytes/pythonRawBytes to
pythonBytesString/pythonRawBytesString in
runtime/syntax/python.vim.
fixes: vim/vim#20812
closes: vim/vim#20827
https://github.com/vim/vim/commit/f88e7191da1a03b2e79a2ba5fbc26f4948bcca81
Co-authored-by: qwavies <qwavsbusiness@gmail.com>
Diffstat (limited to 'runtime/syntax/python.vim')
0 files changed, 0 insertions, 0 deletions