On 6/2/06, Mun Johl <[EMAIL PROTECTED]> wrote:
Hi,
After taking a couple of helpful hints from Eric, and doing a bunch of
experiments, I have isolated some odd behavior to 'laststatus'.
As a reminder, this issue only shows up when I compile vim7 using GTK-1;
it does not occur when I compile with Motif or GTK-2. My system is a
Sun workstation running Solaris 8 and I use gcc 3.3.2 for compilation.
Have you tried both gvim and vim via an xterm?
The problem is that when I compile vim7 using GTK-1, certain characters
need to be typed twice on the _search_ line. Note that it only appears
as if the search line is affected. Text entry and command entry don't
appear to be affected.
I forgot, are you now testing with gvim -u NONE -U NONE ? You
need to be sure that there aren't any plugins or mappings involved.
If I set laststatus to 0 or 1, the problem goes away. If I set it to 2
again, the problem re-appears.
Does the problem correlate to the presence or absence of the displayed
statusline?
I.e. can you have 'laststatus' at '1', and have two or more windows
split so that a statusline is displayed.
Do you have anything interesting in the 'statusline' option?
This doesn't always occur either; some files edit just fine. So there
is some other dependency as well it seems--but I haven't discovered that
yet. But, when it does occur, changing laststatus to 0 or 1 always
corrects the issue.
Is incremental search on?
Also, you could do a binary search (i.e. chop it up into chunks) on an
affected file to try to find out what text is triggering it.
Here's a sample of what I get when I type each letter in the English
alphabet twice in a row (e.g.: aabbccddeeff...):
abbcdeffgghijjkklmmnopqqrßtuvvww×yzz
^
|
this is the greek Beta character (in case it
got lost in the transmission)
Notice how some characters only show up once, and the one greek
character.
Too weird.
Any insights would be appreciated.
Regards,
--
Mun
