diff options
| author | Sean Dewar <6256228+seandewar@users.noreply.github.com> | 2025-07-16 20:44:18 +0100 |
|---|---|---|
| committer | Sean Dewar <6256228+seandewar@users.noreply.github.com> | 2025-07-22 13:36:33 +0100 |
| commit | 9813c00dd376c00c382aaf0a8f0a6d0f45ba2a5d (patch) | |
| tree | 0df1b085cc41c81033081a529a891ca4e4d0a58f /runtime/lua/vim/provider/python.lua | |
| parent | 1d2d6e31a7ea6e5f931b2a92633d18e1ff485f14 (diff) | |
| download | rneovim-9813c00dd376c00c382aaf0a8f0a6d0f45ba2a5d.tar.gz rneovim-9813c00dd376c00c382aaf0a8f0a6d0f45ba2a5d.tar.bz2 rneovim-9813c00dd376c00c382aaf0a8f0a6d0f45ba2a5d.zip | |
fix(window): restore b_nwindows if win_close_othertab keeps window
Problem: can't accurately know if close_buffer directly (e.g: not via autocmds)
decremented b_nwindows. This can cause crashes if win_close_othertab decides to
keep the window after calling close_buffer (if it did not free the buffer), as
b_nwindows may remain out-of-sync.
Solution: change the return value of close_buffer to accurately depict whether
it decremented b_nwindows. Check it in win_close_othertab to avoid a crash.
Similar issues may exist in other places that call close_buffer, but I've not
addressed those here (not to mention only one other place even checks its return
value...)
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions