Ok. So we know three things: The incremental search feature + the gvim/gui input method + the statusline
It would be interesting to try: :feedkeys( "/3\<CR>", "t") ^R=some expression this will tell us if the problem is in the "get char from use" vs the "process char with incsearch". On 6/2/06, Mun Johl <[EMAIL PROTECTED]> wrote:
Hi Eric, Please see my comments below. On Fri, Jun 02, 2006 at 10:42 AM PDT, Eric Arnold wrote: EA> On 6/2/06, Mun Johl <[EMAIL PROTECTED]> wrote: EA> >Hi, EA> > EA> >After taking a couple of helpful hints from Eric, and doing a bunch of EA> >experiments, I have isolated some odd behavior to 'laststatus'. EA> > EA> >As a reminder, this issue only shows up when I compile vim7 using GTK-1; EA> >it does not occur when I compile with Motif or GTK-2. My system is a EA> >Sun workstation running Solaris 8 and I use gcc 3.3.2 for compilation. EA> EA> Have you tried both gvim and vim via an xterm? Note that I am no longer going through Exceed; rather I'm running right on my Sun box. So on my Sun box I have tried running vim within my dtterm. As expected, there is no problem when running vim within the dtterm. EA> >The problem is that when I compile vim7 using GTK-1, certain characters EA> >need to be typed twice on the _search_ line. Note that it only appears EA> >as if the search line is affected. Text entry and command entry don't EA> >appear to be affected. EA> EA> I forgot, are you now testing with gvim -u NONE -U NONE ? You EA> need to be sure that there aren't any plugins or mappings involved. I did try that, and I didn't see the issue after doing so. After that, I started homing in on whether it was the loading .gvimrc or .vimrc that caused the problem; and then which line(s) until I finally landed on my laststatus setting. EA> >If I set laststatus to 0 or 1, the problem goes away. If I set it to 2 EA> >again, the problem re-appears. EA> EA> Does the problem correlate to the presence or absence of the displayed EA> statusline? Yes. If 'laststatus' is 1 and I split the window, the problem shows up. But depending on what file is in the new split window, that window my not experience the problem. But if I have a "problematic" file in both split windows, they will both experience the problem. Also, the same file will not _always_ have the problem. It seems that if I set 'laststatus' to 0 or 1 and then exit and re-open the file with 'laststatus' == 2, I don't see the problem. So I guess that implies that the .viminfo file has some influence. But setting 'laststatus' to 2 and exiting/re-entering doesn't always bring the problem back. Sigh. EA> I.e. can you have 'laststatus' at '1', and have two or more windows EA> split so that a statusline is displayed. EA> EA> Do you have anything interesting in the 'statusline' option? I commented out my specific 'statusline' settings for most of the testing; so that does not seem to make a difference. EA> >This doesn't always occur either; some files edit just fine. So there EA> >is some other dependency as well it seems--but I haven't discovered that EA> >yet. But, when it does occur, changing laststatus to 0 or 1 always EA> >corrects the issue. EA> EA> EA> Is incremental search on? Yes. But, if I turn it off the problem disappears! If I turn it on again, the problem reappears. EA> Also, you could do a binary search (i.e. chop it up into chunks) on an EA> affected file to try to find out what text is triggering it. Heh, wait until you hear this... I took a file that at the time was experiencing the problem. I finally got it to the point that if the file contained the single character "3", then no problem. But if the file had two characters "3.", I'd hit the problem. Other experiments showing file contents and whether or not I saw a problem: "33" : No problem "33." : Problem "33.3" : Problem "333" : No Problem I realize there are MANY other combinations to try; but I don't have that kind of time :) EA> >Here's a sample of what I get when I type each letter in the English EA> >alphabet twice in a row (e.g.: aabbccddeeff...): EA> > EA> >abbcdeffgghijjkklmmnopqqrßtuvvww×yzz EA> > ^ EA> > | EA> > this is the greek Beta character (in case it EA> > got lost in the transmission) EA> > EA> >Notice how some characters only show up once, and the one greek EA> >character. EA> EA> EA> Too weird. Agreed. -- Mun
