[vim/vim] GTK4: cannot resize shell after the window is realized (PR #20269)

5 views
Skip to first unread message

mattn

unread,
May 20, 2026, 8:05:01 PM (2 days ago) May 20
to vim/vim, Subscribed

Under GTK4, gui_mch_set_shellsize() only applied the requested size when the main window had not yet been realized. After realization (e.g. when :set guifont=... triggered a resize via font change), the call became a no-op and the shell stayed at its old size, leaving the command line and lower rows clipped outside the window. Always forward the requested size to gtk_window_set_default_size() so subsequent shell resizes take effect.

Fixes #20264


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/20269

Commit Summary

  • f37fb0b GTK4: cannot resize shell after the window is realized

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/20269@github.com>

Christian Brabandt

unread,
May 21, 2026, 5:01:12 PM (17 hours ago) May 21
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#20269)

@habamax can you confirm this fixes the issue?


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/20269/c4512726896@github.com>

Maxim Kim

unread,
May 21, 2026, 7:10:58 PM (14 hours ago) May 21
to vim/vim, Subscribed
habamax left a comment (vim/vim#20269)

@habamax can you confirm this fixes the issue?

It fixes font re-size issue.


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/20269/c4513490823@github.com>

Reply all
Reply to author
Forward
0 new messages