diff options
| author | Muhammad Arrafif Prikusuma <muhammadarrafif1308@gmail.com> | 2026-06-28 07:08:59 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-06-28 07:08:59 +0800 |
| commit | 35cbf4fbddc5b095bc21fe23fd62f091355e40b0 (patch) | |
| tree | 3fe3256759d8bf2cf88bf6f806e88601e4db4442 /runtime/ftplugin/python.vim | |
| parent | cef31fde6ac77404f778627f1adcca68f905618e (diff) | |
| download | rneovim-35cbf4fbddc5b095bc21fe23fd62f091355e40b0.tar.gz rneovim-35cbf4fbddc5b095bc21fe23fd62f091355e40b0.tar.bz2 rneovim-35cbf4fbddc5b095bc21fe23fd62f091355e40b0.zip | |
fix(autocmd): safely parse buflocal buffer numbers (#40436)
* refactor(autocmd): safely parse buflocal buffer numbers
Replace unsafe atoi with a robust integer conversion when extracting
the buffer number out of a "<buffer=123>" pattern in
aupat\_get\_buflocal\_nr.
This prevents potential silent integer overflows and ensures variables
fit safely within INT\_MAX boundaries before truncation.
* fix(autocmd): use getdigits_int to safely parse buffer numbers
* fix(autocmd): raise error for invalid buffer-local pattern values
When defining an autocommand, an invalid buffer-local pattern format
(such as `<buffer=foo>` or `<buffer=0>`) would previously fall through
silently and default to a generic `<buffer>` tag behavior.
Fix this regression by trapping invalid buffer numbers
early from `aupat_get_buflocal_nr()` and throwing a proper E680 error
to match Vim's runtime validation behavior.
Diffstat (limited to 'runtime/ftplugin/python.vim')
0 files changed, 0 insertions, 0 deletions