On 14/05/09 18:48, 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. 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. > > Thanks for the help! > > :) Michael
You wouldn't really want to check command names and command-line arguments: cp, mv, mkdir, ls, -v, vim, gvim, vimdiff, gvimdiff, gview, etc. are not English words (for any regional variant of English), and shouldn't be checked. The only parts of a shell script which can consistently be assumed to be English text are the comments. Similarly, in an HTML page, the "displayable" text (i.e. the part of the <body> which is not between < and > ) and maybe the comment text, are the only parts which can be assumed to be English (maybe also the title i.e. from <title> to </title> not including the tags themselves). Best regards, Tony. -- Really heard in court in the U.S.A.: Q.: What was the first thing your husband said that morning? A.: He said, "Cathy, where am I?" Q.: And why did that displease you? A.: Because my name is Susan. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
