I have seen this problem, but have not yet reported it as a bug because
I haven't got much information to go on. At work on my Fedora 7 machine
with a self-compiled Vim 7.2.25, I see this problem when I run ``gvim -u
NONE``, then set guifont to some font (it doesn't seem to matter which
one), then create and immediately close a vertical split window (CTRL-W
CTRL-V CTRL-W CTRL-O). The cursor may be restored in any of several
ways, such as re-splitting the window. As a work-around, I've mapped
CTRL-L to a function that does ``let &guifont=&guifont``, which also
seems to restore the missing cursor. When I use the same Vim source
code (7.2 with patches 1-25), I have no problem on my Ubuntu Hardy Heron
machine at home, which is why I'm unsure what kind of bug this might
be. If I leave guifont empty, the problem doesn't occur on the Fedora
machine. I'd been hoping to do some more digging before reporting this
problem because it seems unusual, but I won't have access to my Fedora 7
machine until 2009 (I'm on vacation :-)).
Michael Henry
Hm. I use KDE 3.5.10 release 20.1, but what influence should that have
on a gvim with Gnome2 GUI? (KDE GUI has been retired some time ago,
6.2.something I think).
Best regards,
Tony.
--
Life would be so much easier if we could just look at the source code.
Also, from the link Alien provided there is this set of experimental
results:
Gvim vsplit bug occurs on:
openbox
awesome
fluxbox
kde 4.1
Gvim vsplit does not occurs on:
Gnome 2.24 guess
xfce xfce 4.4.2
So, as Tony suggests, it doesn't seem to be influenced much by choice of
window manager.
I found it interesting that some Fedora 5 users were having the problem
as well. It seemed they were all using Vim 7.2.25 or thereabouts.
It would probably be enlightening to see if Vim 7.2.0 or earlier have
this problem; if not, we could binary search our way to a diff in Vim
that brings about the behavior.
Michael Henry