Zhaojun WU wrote:
Hi, Vimmers,
Just found an interesting problem but don't why.
I am using Debian on my Linux box and used the vim-gtk package before.
I have the settings like:
=========================
if has("gui_running")
set guifont=BitStream\ Vera\ Sans\ Mono\ 11
set guioptions=mei " only display Menu, Tab, and Icon
colorscheme oceandeep
set lines=60 columns=89
"set cursorline " Highlight Current Line in GUI mode
endif
==========================
I set the lines and columns to make it start with a gvim window to
cover half part of my screen (lines=60 and columns=89). This settings
worked fine no matter when I run the "gvim" from the XFCE launch menu
or from a command "$gvim".
Recently, I replaced the "vim-gtk" package with "vim-full", if I
launched it from the XFCE menu, it works like before (give me a 60x89
gvim window). But, if I run "gvim" from my bash prompt, I can get a
window with random-sized gvim window.
I am sure the gvim shortcut in the XFCE launch menu is also pointing
to the "gvim" I ran on the my rxvt.
So, in this case, I am just wondering who actually controls the lines,
cols of my gvim window? Any difference btw vim-full and vim-gtk makes
it happened?
Thanks,
Try
:verbose set lines? columns?
It should tell you where they were last set.
Best regards,
Tony.
--
Sixtus V, Pope from 1585 to 1590 authorized a printing of the Vulgate
Bible. Taking no chances, the pope issued a papal bull automatically
excommunicating any printer who might make an alteration in the text.
This he ordered printed at the beginning of the Bible. He personally
examined every sheet as it came off the press. Yet the published
Vulgate Bible contained so many errors that corrected scraps had to be
printed and pasted over them in every copy. The result provoked wry
comments on the rather patchy papal infallibility, and Pope Sixtus had
no recourse but to order the return and destruction of every copy.
