> I am using gvim and there's a little problem bothering me for a
> long time.
on which platform are you using gvim? Windows, OS X, Linux (or
something different altogether)?
Nico
I can reproduce some weird strange behaviour by starting gvim,
selecting Window Menu->Advanced->Fullscreen in KDE and then
doing :tabnew. Is that what you mean?
Nico
I remember looking into similar issues before. If I remember correctly,
KDE sizes the gvim window to fill the screen and then gvim resizes to
the appropriate size in order to prevent having columns/lines cut off.
This makes the gvim window no longer "maximized" according to KDE and
therefore not size constrained. Now, when you create a tab in Vim, the
window size grows to accomodate the new tab bar and KDE doesn't push
back with size constraints.
It seems that there is some miscommunication between gvim and KDE.
Although, it'd probably be better in general to have gvim maintain the
size of the application window and reduce the size of the editing area
when creating the tab bar. This is all simple observation as I haven't
had time to dig into the relevant internals to see how things are coded
to behave.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jame...@jamessan.com>
I think this bug has been fixed a few weeks ago by patch 7.1.244:
ftp://ftp.vim.org/pub/vim/patches/7.1/README
I was having the same issue and it's no longer the case.
I'm using gVim 7.1.264 on Linux (GTK1, KDE 3.0.3, font Adobe Courier
Medium 14 ISO-10646-1).
With a maximized Windows (and KDE toolbar visible) I have :
:set lines? columns?
lines 42
colunms 110
:tab help
:set lines? columns?
lines 42
colunms 80
tabs takes about two lines on screen and Vim command line becomes hidden
by KDE toolbar.
--
Patrick Texier
vim:syntax=mail:ai:ts=4:et:tw=72
Just a comment on building gvim: you don't have to. All you need is a
symbolic link. Assuming vim is in /usr/local/bin, all you need to do is
(as root):
cd /usr/local/bin
ln -s /usr/local/bin/vim gvim
Now, the "make install" process generally does this itself; so I'm
wondering why it wasn't done for you?
Regards,
Chip Campbell
> I appreciate for you replay. Since Gentoo has only max version 7.1.213 of
> gvim currently , so I downloaded all the patches prior to 7.1.265 and built
> it myseltf.
Thanks for you tiny screen copy attachement, it's my yesterday test.
I'm using now text tabs with the following line in my .vimrc:
set guioptions-=e (for ultimates wimmers ;-) set guioptions=)
GUI tabs have at least two bugs :
- open tab uses startup columns option and not current:
$ gvim -c":set lines=25 columns=60"
maximazes window (for me 42 x 110)
:tab new [or any tab command like tab help or tabedit]
You get 60 columns (and not current value)
- lines ignore KDE toolbar.
> Compiled by root@localhost
root is needed only for make install
> Normal version with GTK2 GUI. Features included (+) or not (-):
use ./configure --with-features=big (or huge)
--
Patrick Texier,
Frulon, 36190 Orsennes, France (46°31'N, 01°41'E)
<http://www.genindre.org>
<http://www.genindre.org/cgi-bin/geneweb.cgi?b=pt>
What you built is a GUI version of Vim. By default, on Linux, it is named vim
because it can work either in console mode or in GUI mode. To be able to
invoke it as any of the "alternate names" mentioned under ":help ex", do the
following in the bash shell (once: the next time you compile Vim, you won't
have to do it again):
cd /usr/local/bin
for p in vi ex exim view gvim gex gview rvim rview rgvim rgview evim eview
vimdiff gvimdiff; do ln -sv vim $p; done
-- from "for" to "done" is one long line; you may remove any program names
which you don't want to install, e.g. remove exim if you use the "other" exim
for handling mail.
The above is what is meant by the following sentence in the help:
On Unix, you would normally have one executable called Vim, and links from the
different startup-names to that executable.
Best regards,
Tony.
--
Every solution breeds new problems.
If Gentoo's vim/gvim are elsewhere (e.g. in /usr/bin/vim with runtime files in
/usr/share/vim/vim71/) then you can "make install" with no problems: it will
install your own-compiled Vim in /usr/local/bin (which is earlier in the
$PATH) with runtime files in /usr/local/share/vim/vim71/. Any package
dependencies will still be fulfilled by Gentoo's Vim, but invoking "vim" will
run yours -- which shouldn't be a problem if it's a Big or Huge version --
"bigger" than Gentoo's, so it has at least the same capabilities.
>
> Maybe the bug exists in vim's GUI version (it has nothing to do with
> gvim Ex, gvim just adds menus and toolbars). It's the same GUI tabbar no
> matter whether in vim -g or gvim. Am I get it right?
Yes. If your Vim is compiled "with GUI", "vim -g" is identical with "gvim"
(assuming gvim redirects to vim). If it isn't, neither will work.
[...]
> Best regards,
> Plan
Best regards,
Tony.
--
Certainly there are things in life that money can't buy, but it's very funny--
Did you ever try buying them without money?
-- Ogden Nash