aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2026-02-20 09:17:54 +0800
committerzeertzjq <zeertzjq@outlook.com>2026-02-20 09:17:57 +0800
commitc67248988b8685a894128cfcd8c3629cc7ff1886 (patch)
tree807fea7d661467e6eabc4245cd1259f75cb12fcc /runtime/lua/vim/provider/python.lua
parentc78e276881eb94aae749a6832c39bbc3622e4440 (diff)
downloadrneovim-c67248988b8685a894128cfcd8c3629cc7ff1886.tar.gz
rneovim-c67248988b8685a894128cfcd8c3629cc7ff1886.tar.bz2
rneovim-c67248988b8685a894128cfcd8c3629cc7ff1886.zip
vim-patch:342ae5f: runtime(progress): Use setlocal for expandtab
The Progress syntax file gained `set expandtab` in 4c3f536f4 (updated for version 7.0d01, 2006-04-11). The Progress language itself doesn't distinguish between tabs and spaces for indentation, so this seems like something that should be left to user preference; but the setting is accompanied by the comment "The Progress editor doesn't cope with tabs very well", so there may be reason to keep it. However, using `set` means that any new buffers created after editing a Progress file will also have `expandtab` turned on, which is likely contrary to a user's expectations. We should use `setlocal` instead to avoid this. closes: vim/vim#19458 https://github.com/vim/vim/commit/342ae5f8aa612179f9390c21a8129a393a995b1a Co-authored-by: Daniel Smith <daniel@rdnlsmith.com>
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions