Hi Eric,
Please see my comments below.
On Wed, May 24, 2006 at 04:03 PM PDT, Eric Arnold wrote:
... Text Deleted ...
EA> >here's what was echoed:
EA> >
EA> >abdfgijkmoqsuvwyz
EA> >
EA> >But when I inserted the alphabet into the body of the file, all
EA> >characters were present. Also, on the search line, if 'a' is not
EA> >entered as the first character, then it won't display either.
EA>
EA>
EA> I asked the question because it sounds like the problem is either
EA> 1) something is not transmitting the key
EA> 2) something is eating the key
EA>
EA> First of all, I'll assume that you've checked that your keyboard isn't
EA> wonky.
Correct; keyboard is not wonky.
EA> If the case is 2), the main culprits are usually mappings or
EA> abbreviations which are grabbing the key for something.
EA>
EA> If the "a" key is consistently not received except in the first
EA> column, then you have something non-intermittent to play with.
I'm seeing behavior that is kind of all over the place when I compile
with gtk. For example, some chars don't show up when typed as part of
the search text; but they do show up if I type them as part of a command
entry string.
EA> >Interestingly, I just noticed that I typically see this behavior when
EA> >the filetype is not set ("filetype="). I set the filetype=mail on the
EA> >problematic file, and the problem went away. I did not close and reopen
EA> >the file either. So I guess it's not an Exceed or GTK issue after all.
EA>
EA> Possibly, if the problem is consistently fixed by changing the
EA> filetype.
Sadly, new data shows that the changing the filetype to mail does not
always work after all. At this time, I have no data correlating the
issue to a specific filetype.
EA> >In that scenario, I'd be logged in on my PC and start the Exceed X
EA> >server. Then, I'd open a terminal on my Sun box and export the terminal
EA> >to my PC. From that terminal I'd issue a vim -g command and export the
EA> >vim window to my PC.
EA>
EA> Try starting an Xterm on the Sun, displayed to the pc, and running the
EA> non-gui vim through the Xterm.
I'm currently trying to get my system updated to GTK-2, to see if that
helps. Once I get the running, and if I still see the issue, I'll try
your suggestion.
EA> >But--as mentioned above--I no longer believe Exceed or GTK are possible
EA> >suspects. Maybe I should be looking at my plugins or something. I'll
EA>
EA> I still hold out the possibility that you have a flow control problem
EA> somewhere in the stream. Since ^S / ^Q are flow control characters
EA> for some schemes, and ^Q in Vim will eat characters (if exchanged with
EA> ^V with the mswin behavior), it is a suspect.
But then I would of expected the same issue when compiled with Motif.
EA> One thing you should try if you haven't already is
EA>
EA> gvim -u NONE -U NONE --noplugin
EA>
EA> which should give you a clean process to play with (annoying clean,
EA> actually...you probably want to set nocp at least).
Another good idea; I haven't tried this yet simply because I almost
can't use vim without all of my customizations. But I'll keep it in
mind after the GTK-2 effort.
Regards,
--
Mun
