On 2011-07-06, Alexandre Provencio wrote:
> 
> 
> On Wed, Jul 6, 2011 at 1:38 PM, Gary Johnson <[email protected]> wrote:
> 
>     On 2011-07-06, Alexandre Provencio wrote:
>     >
>     >
>     > On Wed, Jul 6, 2011 at 11:36 AM, Gary Johnson wrote:
>     >
>     >     On 2011-07-06, Alexandre Provencio wrote:
>     >     > I can also confirm that this is really an issue with the Ubuntu
>     Natty's
>     >     > version. I've just run a livecd, installed vim-gnome, set .vimrc 
> to
>     'set
>     >     spell
>     >     > spelllang=en' and the same behavior described occurs.
>     >
>     >     That's very good--that should give us a starting point that other
>     >     people can use to verify and/or diagnose this problem.  I'm losing
>     >     track of exactly what behavior you're seeing, though.  After
>     >     creating a ~/.vimrc file containing only "set spell spelllang=en",
>     >     what steps do you take and what do you observe?  Give enough detail
>     >     that anyone could unambiguously repeat your steps.  If you're
>     >     opening a file that contains spelling errors that aren't being
>     >     highlighted as you expect, include the contents of that file here,
>     >     or at least some small part of it that exhibits the problem.
>     >
>     > Ok.
>     >
>     > 1) Create (or use existing) 2 files with spelling errors
> 
>     I first moved my ~/.vim and ~/.vimrc aside and created a new
>     ~/.vimrc containing only this line:
> 
>        set spell spelllang=en
> 
>     Then I created two files containing spelling errors.  File one
>     contains
> 
>        The doog is brown.
> 
>     and file2 contains
> 
>        The burd is blue.
> 
>     > 2) Start vim (or gvim) with no arguments. Start typing words which does
>     not
>     > exist, you'll confirm that the words get highlighted by the spell 
> checker
> 
>     I started vim without any arguments and started typing this:
> 
>        The qick brown
> 
>     The word "qick" is highlighted.
> 
> I've just found out that you should not type any words on the step2 in order 
> to
> reproduce the bug. Go directly to step three, and this way you won't see the
> E37 message.
> Please repeat the steps with these corrections.

OK, I just did.  I see it!  Not with the ~/bin/vim version 7.3.189
that I built myself, but with the /usr/bin/vim version 7.2.148 that
came with this Fedora 11 system.

    /usr/bin/vim --noplugin -u ~/.vimrc.ap
    :e file1

No highlighting of the misspelled word!  (I moved your one-line
.vimrc to .vimrc.ap so that I could have my configuration back.)

    :e file2

Misspelled word is now highlighted.

That the problem appears in 7.2.148 (and for you in 7.3.035) but not
in 7.3.189 suggests that it was a bug that has been fixed.  Unless
the Ubuntu repository has a newer version, compiling your own is
probably the best solution.

I'm glad you stuck with this.

Regards,
Gary

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Reply via email to