On Sunday 08 August 2010 11:25:43 am Tony Mechelynck wrote: > On 07/08/10 17:24, Aljosa Mohorovic wrote: > > under kde i can't get vim to maximize like other windows. > > if i understood correctly this is because vim calculates space font > > occupies and it resizes window to match font space. > > is there a way to tell vim to ignore font space and just maximize > > window even if it will display only half of character/font? > > > > Aljosa Mohorovic > > Hm, using > > :set lines=99 columns=999 > > will "almost" maximize gvim, to maybe one character cell of the screen > borders (gvim recomputes 'lines' and 'columns' to what is available). > Then, click the square icon near the right end of the titlebar. This > will "really" maximize gvim. But it will not crop the font: there may be > an empty half-line or so left unused inside the bottom of the gvim > window. The advantage is that from then on (and with recent versions of > GTK2 gvim, at least), if you change 'guifont' to set a larger *or > smaller* font, the gvim screen will remain maximized, decreasing *or > increasing* 'lines' and 'columns' to what the new font size allows. Or > at least that's what I see under Gnome. > > > Best regards, > Tony.
This doesn't seem to help in under kde. When you click maximize, for a split second the window maximizes, it then immediately resizes to a full character distance from the bottom, and then from the right. This leaves a full character border on both sides and since the window is not maximized, you have to be careful not to close the window behind it if you try to click on the close button. This is reported on kde's bugzilla page as bug 158974. However, it doesn't seem clear if this is a gvim or kwin problem. For what its worth, emacs has the same problem. I tried to look at this a few days back, when vim finishes with gui_resize_shell in gui.c, the window is fully maximized, however, before it finishes returning through the gtk code, another resize is triggered again. I didn't have the setup to actually check if kwin is triggering it, or if it is a gtk issue. -- Daniel -- You received this message from the "vim_use" 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
