The problem I have is not the same as the ticket. For one thing, I get it "every time", lnot "occasionally"; also I am on X11, not Wayland.
Typing "gvim -N -u NONE" in a bash shell opens gvim with menu and toolbar but no vertical space for a future editfile; in order to see a command line I have to maximize the screen manually. With just "gvim" my vimrc, which removes the toolbar display, is sourced, and the GUI window is even smaller, just enough for the menubar. In this case there is (every time) a message on the terminal where gvim was started: (gvim:1066803): Gtk-CRITICAL **: 11:46:29.128: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed but not when sourcing the vimrc is avoided by one of -u NONE -u NORC or -u DEFAULTS. After -u DEFAULTS the GUI opens with a menubar, toolbar, and even a visible comand-line, but no more than one line of edit window (or is it an empty status line ?) above it On Fri, May 9, 2025 at 10:56 AM Christian Brabandt <cbli...@256bit.org> wrote: > > Hi, > Can you both please respond to the mentioned ticket? Is this that bad, > that we need to revert? > > Thanks, > Chris > > On Fri, 09 May 2025, Tony Mechelynck wrote: > > > P.S. Oh, and X11, I don't use Wayland. > > > > Best regards, > > Tony. > > > > On Fri, May 9, 2025 at 9:58 AM Tony Mechelynck > > <antoine.mechely...@gmail.com> wrote: > > > > > > This seems to be the same problem as the one I reported a few minutes > > > ago as «"E36 Not enough room" while sourcing handcrafted session > > > file». I am now with gvim 9.1.1374 but it has been happening for a > > > couple of days in earlier versions. Huge version with GTK3 GUI. The > > > GUI opened with just enough height and width for the menubar, and gave > > > E36 while sourcing a :new command with filename (and refused to open > > > that file) until I manually maximized the GUI. Adding a line "set > > > lines=99 columns=999" before the first :new command in the session > > > file made the problem disappear. I already had an autocommand "au > > > GUIEnter * set lines=99 columns=999" (without the quotes), which seems > > > not to be acted upon, in my vimrc. > > > > > > Best regards, > > > Tony. > > > > > > > > > On Fri, May 9, 2025 at 12:25 AM tooth pik <toothp...@gmail.com> wrote: > > > > > > > > yes that looks like it > > > > > > > > what's wayland? is it like x11 or kde? > > > > > > > > opensuse 15.6 > > > > > > > > On Thu, May 8, 2025 at 4:52 PM Christian Brabandt <cbli...@256bit.org> > > > > wrote: > > > >> > > > >> I still don't understand. Is this your issue: > > > >> https://github.com/vim/vim/issues/17279 > > > >> > > > >> Are you also on Wayland? > > > >> Are those just warnings? Or does it prevent resizing? > > > >> > > > >> Thanks, > > > >> Chris > > > >> > > > >> On Thu, 08 May 2025, tooth pik wrote: > > > >> > > > >> > ordinarily, when i start a raw gvim with no size specified, it > > > >> > assumes the same > > > >> > size as the X-window it was started from -- i am attaching a picture > > > >> > of what > > > >> > happens now, complete with error messages > > > >> > > > > >> > i get the same tiny window if there's a -geometry request in the > > > >> > starting script, > > > >> > and the same errors > > > >> > > > > >> > On Thu, May 8, 2025 at 1:28 AM Christian Brabandt > > > >> > <cbli...@256bit.org> wrote: > > > >> > > > > >> > Hi, > > > >> > And what exactly is the issue, don't understand what you mean > > > >> > with > > > >> > "won't open its requested size"? Can you share a picture and how > > > >> > to > > > >> > reproduce? Did you try `gvim --clean`? k > > > >> > > > > >> > Does it work, if you checkout pqatch v9.1.1367 instead? Perhaps > > > >> > there is > > > >> > an issue with v9.1.1368? > > > >> > > > > >> > Thanks, > > > >> > Chris > > > >> > > > > >> > On Wed, 07 May 2025, tooth pik wrote: > > > >> > > > > >> > > vim is 9.1.1369 > > > >> > > gtk3-devel is 3.24.34 > > > >> > > anything else? > > > >> > > > > > >> > > On Wed, May 7, 2025 at 4:40 PM Christian Brabandt > > > >> > <cbli...@256bit.org> wrote: > > > >> > > > > > >> > > > > > >> > > On Wed, 07 May 2025, tooth pik wrote: > > > >> > > > > > >> > > > all of a sudden gvim won't open to its requested size, > > > >> > while various > > > >> > > > "gtk_distribute_natural_allocatio: assertion > > > >> > 'extra_space >= 0' failed" errors > > > >> > > > go to stdout > > > >> > > > > > >> > > What version? And what is your GTK version? > > > >> > > > > > >> > > Thanks, > > > >> > > Christian > > > >> > > > > >> > Mit freundlichen Grüßen > > > >> > Christian > > > >> > > > >> > > > >> > > > >> Mit freundlichen Grüßen > > > >> Christian > > Mit freundlichen Grüßen > Christian > -- > Survivulousness: > The tendency to visualize oneself enjoying being the last > person on Earth. "I'd take a helicopter up and throw microwave ovens > down on the Taco Bell." > -- Douglas Coupland, "Generation X: Tales for an Accelerated > Culture" -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/CAJkCKXvZTWZnjMBPvL5mAUkObG0EqxB2mPw%2BbFLO%3DkZ8%3D%2BFEsg%40mail.gmail.com.
