aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorSean Dewar <6256228+seandewar@users.noreply.github.com>2026-03-12 17:31:37 +0000
committerSean Dewar <6256228+seandewar@users.noreply.github.com>2026-03-14 20:48:32 +0000
commit853eea859fd31e7ffcbe6d09e1281f77f279f7a0 (patch)
tree3d7f60817e9922eb18be22f1fa7fb6b74672c2b0 /runtime/lua/vim/provider/python.lua
parent094b297a3b33f6336a825818bfd6a53b25273ac8 (diff)
downloadrneovim-853eea859fd31e7ffcbe6d09e1281f77f279f7a0.tar.gz
rneovim-853eea859fd31e7ffcbe6d09e1281f77f279f7a0.tar.bz2
rneovim-853eea859fd31e7ffcbe6d09e1281f77f279f7a0.zip
fix(api): disallow moving window between tabpages in more cases
Problem: more cases where it may not be safe to move a window between tabpages. Solution: check them. Rather speculative... I haven't spend much time looking, but I didn't find existing code that sets these locks to skip checking win_valid. (what I did find called it anyway, like in win_close) Still, I think it's a good precaution for what future code might do. If the fact that nvim_win_set_config *actually* moves windows between tabpages causes unforeseen issues, "faking" it like ":wincmd T" may be an alternative: split a new window, close the old one, but instead also block autocmds, copy the old window's config, and give it its handle?
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions