Mun Johl wrote:
> I'm resending the following email with a more descriptive title.
>
> On Fri, Jun 02, 2006 at 12:17 PM PDT, Charles E. Campbell, Jr. wrote:
>
> ... Text Deleted ...
>
> CECJ> I suggest narrowing down the problem.
> CECJ>
> CECJ> vim -u NONE -U NONE
> CECJ>
> CECJ> for starters. Then try to source in a minimal file (I believe you
> CECJ> mentioned something about laststatus).
> CECJ> If you get the double strike effect, you've got something that others
> CECJ> have a chance at duplicating, and in particular,
> CECJ> Bram M has a shot at fixing.
>
> I've narrowed this down to the minimum configuration that causes a
> problem for me. It's these two settings:
>
> set spell
> set incsearch
>
> If I start vim thusly:
>
> % vim -g -u NONE -U NONE --noplugin <filename>
>
> And then source a file with the two above settings--or just set them in
> the vim session--I start getting the weird behavior in my search line.
>
> Again, I see this with my GTK-1 build on Solaris; but not with a Motif
> or GTK-2 build. Unfortunately for me, I prefer the GTK-1 build because
> it is so much faster to load than my Motif build. And it doesn't have
> the font issues like GTK-2.
I don't see this problem. I suspect it has something to do with an
input method. Did you check the 'imsearch' option?
--
Did you ever stop to think... and forget to start again?
-- Steven Wright
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
