Monday, July 4, 2011

Re: Spell checker not working for files opened with ":e"



On Mon, Jul 4, 2011 at 6:35 PM, Gary Johnson <garyjohn@spocom.com> wrote:
On 2011-07-04, Alexandre Provencio wrote:
> Hello everyone, the spell checker here is is not working when opening files
> with ":e", but it works if I ":e" again on the same viewport, or using the
> ":tabe" or calling the file as an argument for vim as in "vim filename" (same
> for gvim).
>
> I've already tried leaving only "set spell spelllang=en" on vimrc, and renaming
> the plugins folder, and that behavior does not change.

If I'm understanding you, you have renamed ~/.vim and you have
created a ~/.vimrc containing only that command above,
That is correct.
 
then when you
start vim as just

   vim

you have spell-checking enabled,
Well I don't know if it is enabled on this point, what i meant was that if i launch vim with a file as an argument, as in "vim filename.txt", the spell check visually works for this file
 
but when you open a file using

   :e filename

spell-checking is no longer enabled.
Yes. But if i open a second file with :e again, it does work.
 

OK then.  When you first start vim, execute

   :verbose set spell?

You should see

 spell
       Last set from ~/.vimrc

Then open a file using ":e" and again execute

   :verbose set spell?

What do you see?
I've made this test as you said and also for a second file opened with :e, because as I said above, the spell checking works on this one. On the three situations the same message is returned:
  spell
        Last set from ~/.vimrc (but this text on my local language, pt-br)

Regards,
Gary
Thanks for your attention 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

--
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

No comments:

Post a Comment