aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorGregory Anders <greg@gpanders.com>2025-08-08 07:51:22 -0500
committerGitHub <noreply@github.com>2025-08-08 07:51:22 -0500
commitb1679f0ab6a3f28ffb1aaa08776eff714d6e00b5 (patch)
treed3feaab3d4511aa9f45179718d992923d7d60785 /runtime/lua/vim/provider/python.lua
parent69cc16d917e7f5842580fd923fa3060067d96926 (diff)
downloadrneovim-b1679f0ab6a3f28ffb1aaa08776eff714d6e00b5.tar.gz
rneovim-b1679f0ab6a3f28ffb1aaa08776eff714d6e00b5.tar.bz2
rneovim-b1679f0ab6a3f28ffb1aaa08776eff714d6e00b5.zip
fix(tui): do not remove SIGWINCH handler when resize events are enabled (#35221)
When Nvim is started in one terminal emulator, suspended, and later resumed in a different terminal emulator (as can happen when using e.g. a multiplexer), the new terminal emulator will not have all of the same modes enabled that the original terminal emulator had. This is a problem in particular for in-band resize events because we were disabling the SIGWINCH signal handler when we determined that the terminal supported this mode. However, if the new terminal does not support this mode then the SIGWINCH handler remains disabled, and Neovim no longer properly resizes. Instead of disabling the SIGWINCH handler, we track the state of the resize events mode internally. If the mode is enabled then we return early from the SIGWINCH handler before performing any ioctls or other system calls. But if the mode is not enabled we proceed as normal.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions