John Doe wrote:
I don't know if I am in error, but ':set lines=999 columns=999' from
.vimrc does not work for me under KDE 3.5. It works in ex mode, after
everything is loaded, but not from the .vimrc file (and yes I am using
gvim). There are also some notable strange effects:
au GUIEnter * set lines=999 columns=999
seems to really make gvim think there are so many columns and lines:
word-wrap is turned off and command line disappears, but it resizes the
gvim's window ok.
the only thing that works for me is:
au CursorHold * exe ':set lines=999 columns=999 | au! CursorHold', which
does the resizing after a delay, but sometimes even this produces the
aforementioned strange effect.
In short, under KDE, :set lines=999 columns=999 works for me after
everything "settles down", but not before. I am using gvim 7.0.17.
I'm using gvim under kde too (currently gvim 7.0.191; "rpm -qa |grep kde"
outputs a lot of things, among which "kdebase3-SuSE-9.3-39.7" and
"kdebase3-devel-3.4.0-28"); my vimrc includes
set nocompatible
[...]
runtime vimrc_example.vim
[...]
if has("gui_running")
if has("gui_gtk2")
set gfn=SUSE\ Sans\ Mono\ 9
elseif has("gui_kde")
set gfn=SUSE\ Sans\ Mono/9/-1/5/50/0/0/0/1/0
elseif has("x11")
set gfn=-*-lucidatypewriter-medium-r-normal-*-*-100-*-*-m-*-*
else
set gfn=Lucida_Console:h10:cDEFAULT
endif
[...]
set lines=99999 columns=99999
[...]
endif
[...]
where the [...] represent omitted sections.
gvim always starts maximized. Also (the rare times when I use it) kvim 6.2.14
(a version of gvim 6.2.14 with kde patches to use Qt rather than GTK, Motif,
etc.).
Best regards,
Tony.
--
"I argue very well. Ask any of my remaining friends. I can win an
argument on any topic, against any opponent. People know this, and
steer clear of me at parties. Often, as a sign of their great respect,
they don't even invite me."
-- Dave Barry
