On Thu, May 14, 2009 at 12:48 PM, Michael Repucci wrote:
>
> Thanks for the toggle tips. Those are quite useful.
>
> Upon further usage of spell, I noticed that for *.sh and *.html files
> I do, sometimes, get misspelled highlighting, but it seems context
> specific.

Yes, the syntax files can specify that certain regions are not to be
spell checked, and certain regions are.  This is common, since in most
languages, spell checking variable names would be really annoying, and
in HTML, spell checking tag names would quickly become annoying.

> Namely, for *.sh, spelling is checked in comments or in
> quotes, when not a variable name, etc.; basic commands and paths are
> not spell checked. I can understand, fundamentally, how this is
> useful, but what if I wanted to change this feature. Where would I do
> that? This context-specificity is also true, it seems, in *.html
> files.

Well, like I said, this extra refinement is built into the syntax
files, meaning that you can either copy each offending syntax file to
your ~/.vim/syntax directory and remove the @NoSpell's from the file,
or if you can go without syntax highlighting while spell checking,
just turn it off when you want to see misspellings in variable names
(:syntax off) and turn it back on when you're done (:syntax on).  If
that's an acceptable solution, it could be tweaked to be tied into one
of the "toggle spellcheck" suggestions, and to only disable or disable
syntax highlighting for the currently active buffer, instead of for
all.

> Thanks for the help!
>
> :) Michael
>
> On May 14, 10:05 am, Charles Campbell <[email protected]>
> wrote:
>> Michael Repucci wrote:

In the future, please bottom post on this mailing list.  It's
established list convention to always type replies below the part of
the message that you're replying to.

~Matt

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to