> Another thing I did forget to mention is that we're looking to use codespell > As an auxiliary tool to catch common misspellings in the code, and > include it as an auxiliary tool that makes us avoid mistakes, just like > pylint, reindent.py and autopep8 are used. This also means we'll have > more massive, full tree reaching commits. I'd like to do this sooner > rather than later, and it also means more rebased pull requests.
codespell is interesting because we can customize to chatch the errors we used to do. I would say that aspell is something good to use too. Running "aspell check something.py" can catch much more syntax errors, but unfortunately aspell is not aware of Python language syntax. Anyway, just a few tips to use a spell checker on Vim or Emacs. * sudo yum install aspell (just in case) * On Emacs, you can spell checking by M-$ (the current world) or M-x ispell-buffer (the whole buffer). * On Vim, you can highlight incorrect words by using :set spell spelllang=en ]s and [s jump to through words and z= list suggestions. Another alternative is to directly call aspell[1]: " Maps F12 to aspell checker. map <f12> :w!<CR>:!aspell check %<CR>:e! %<CR> Hope this help. -- Rudá [1] https://www.linux.com/learn/tutorials/357267:using-spell-checking-in-vim _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
