aboutsummaryrefslogtreecommitdiff
path: root/test/functional/vimscript/executable_spec.lua
diff options
context:
space:
mode:
authorSean Dewar <6256228+seandewar@users.noreply.github.com>2025-10-05 18:17:43 +0100
committerSean Dewar <6256228+seandewar@users.noreply.github.com>2025-10-05 23:30:23 +0100
commit7923e847ca5db131c22cef9f8d93454f5b6a47de (patch)
tree8028aa4b32ad747d4c7901324cc9e3e444d02e83 /test/functional/vimscript/executable_spec.lua
parenta4a88381780a400ebb77cee52e7acb35a2a48cc6 (diff)
downloadrneovim-7923e847ca5db131c22cef9f8d93454f5b6a47de.tar.gz
rneovim-7923e847ca5db131c22cef9f8d93454f5b6a47de.tar.bz2
rneovim-7923e847ca5db131c22cef9f8d93454f5b6a47de.zip
vim-patch:9.1.1831: stray vseps in right-most 'winfixwidth' window
Problem: vertical separator of 'winfixwidth' windows may remain if they become right-most windows from closing windows to the right. Solution: Don't implicitly rely on frame_new_width to fix vseps, as the call may be skipped for 'winfixwidth' windows to preserve their width; do it explicitly in winframe_remove (Sean Dewar). Note that I prefer win_new_width here over setting w_width directly, which would've previously been done by win_split_ins after frame_add_vsep, as this wasn't true for winframe_remove. Though the equivalent issue of bottom 'winfixheight' windows leaving stray statuslines with &ls=0 doesn't seem to exist, test it anyway. closes: vim/vim#18481 https://github.com/vim/vim/commit/620c6556778a0df15be4fa33647fff1f6ab36255 Nvim: calling win_new_width over setting w_width directly is especially important in making sure stuff like w_view_width is correct here. Co-authored-by: Sean Dewar <6256228+seandewar@users.noreply.github.com>
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions