Version: (using KDE 4.0.2) Installed from: Debian testing/unstable Packages OS: Linux If you try to maximize GVim, it immediately resizes itself smaller so that its geometry will be a multiple of its character size. If you set "strictly obey geometry" it will resize in the same way when you use maximize the first time, then if you maximize again it will become slightly larger, and the third time it will set itself as maximized, but you still will be able to see around the window and click on windows that are behind. Both GVim and Emacs had similar behavior in KDE 3.5.9, but Emacs is working properly in KDE 4.0.2
GNU Emacs works in 4.0.2 but XEmacs behaves like GVim
I can confirm this happening with gvim-7.2 and emacs-gtk-22.3 on KDE 4.1.3 in Gentoo.
Confirmed on 4.1.96 (KDE 4.2 RC1), with gvim 7.2.069
Still presents in 4.3.3, gvim 7.2.303
*** This bug has been confirmed by popular vote. ***
*** Bug 227967 has been marked as a duplicate of this bug. ***
*** Bug 233921 has been marked as a duplicate of this bug. ***
Does this bug need to be filed upstream (on gvim itself) - or is the bug going to be resolved at KDE level ?
Confirmed no ability to un-maximize, and no benefit of forcing "strictly obey geometry", in Fedora 12 with KDE 4.4.2 for all these apps: gvim (vim-X11) 7.2.411, emacs 23.1.1, Terminal 0.4.2-2 But no such problems for xemacs 21.5.29, for me.
I also have that issue with GNU Emacs. I tried various combinations of the window-specific settings "Ignore requested geometry" and "Strictly obey geometry", but that doesn't seem to make any difference here. I'm using KDE 4.5.1.
http://svn.reviewboard.kde.org/r/5871/
SVN commit 1208120 by luebking: adjust strict geometry policies http://svn.reviewboard.kde.org/r/5871/ BUG: 158974 CCBUG: 252314 @Jorge: please see the request description and check whether this allows you to fix your bug in case, don't forget to close it ;-) M +6 -7 geometry.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1208120
There is a regression of bug Bug 252314 in KDE 4.7 beta 1. I seem to remember these bugs were tightly related, so chances are there is a regression of this one too.
no, gvim is not affected and can be made to either be maximized but not covering the entire screen (default) or maximized & covering the entire screen (forcing the geometry to not be strictly obeyed)