diff options
| author | zeertzjq <zeertzjq@outlook.com> | 2026-03-17 08:02:32 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-03-17 00:02:32 +0000 |
| commit | 9ab6c607ccc73f66ab90721f956c98bbca5cf267 (patch) | |
| tree | 6177ff9f40fa94b0535c89e1b1e8f612ab7c10ec /runtime/lua/vim/provider/python.lua | |
| parent | 6edae880528b7a1494a7610b07e4415d68c463ff (diff) | |
vim-patch:9.2.0180: possible crash with winminheight=0 (#38335)
Problem: possible crash with winminheight=0
(Emilien Breton)
Solution: Use <= instead of < when checking reserved room in
frame_setheight() to correctly handle the zero-height
boundary case (Hirohito Higashi).
In frame_setheight(), when shrinking the current window and the only
other window has 'winfixheight' with 'winminheight'=0, room_reserved
was not cleared because the condition used '<' instead of '<='.
The freed rows were discarded, leaving fr_height sum less than
topframe fr_height. Subsequent resize operations then computed a
wrong room_cmdline that expanded topframe beyond the screen, causing
a crash.
fixes: vim/vim#19706
closes: vim/vim#19712
https://github.com/vim/vim/commit/a5d9654620648ea6d3f2f8dc2a3e42de219cf860
Co-authored-by: Hirohito Higashi <h.east.727@gmail.com>
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions
