Hi, On Thu, Jun 25, 2009 at 12:31:26AM -0600, Ondrej Certik wrote: > > On Wed, Jun 24, 2009 at 8:35 PM, Aaron S. Meurer<asmeu...@gmail.com> wrote: > > > > I think one thing we need to do is go through and spellcheck and > > grammar check (for those of us who are native english speakers) all of > > the documentation, and maybe the comments too. I know I see errors > > all of the time, and most people probably do not use a spellchecker in > > their editor (even I am guilty of this). Is there an easy way to pull > > all of these into a text document that can be run through spellchecker > > and put back again afterwords? > > That'd be really helpful, thanks a lot. It's not only about spell > checker, but also > about word order and articles (like "code" vs "a code") etc. >
And could be also about initialize vs. initialise (US vs. UK).
> As to spellchecker, I think there is some package to vim, but what I
> usually do, I just load the whole file in openoffice, see where the
> errors are, correct them in openoffice, save it and then use "git
> diff" to see if openoffice save the file correctly and if it didn't
> (e.g. it spolied lineends and other things) I use "git add -p" to only
> add the word corrections.
>
To check spelling you can use aspell in Python mode, e.g.
aspell --mode=py -x -c sympy/polys/polynomial.py
Since version 7.2, ViM has built-in spellchecker and native support for
Python. I use it with the following code
function! ToggleSpell()
if &spell
set nospell
echo 'Spell checking disabled ...'
else
set spell
echo 'Spell checking enabled ...'
endif
endfunction
nnoremap <f2> :call ToggleSpell()<cr>
to turn on/off checking using F2 key. The only thing to do is to teach
ViM not to complain about function or class names (among others). Maybe
I could use ctags database for this purpose.
We should also check spelling in git commit messages. If you use ViM to
prepare commits then you get spellchecking for free.
--
Mateusz
signature.asc
Description: This is a digitally signed message part
