Collin Funk <collin.fu...@gmail.com> writes: > Hi Simon, > > Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org> writes: > >> I've been using 'codespell' to find typos in several projects for a long >> time, via ad-hoc syntax-check rules in cfg.mk. I tried to clean up the >> rule and make it generic enough to be useful everywhere. I've pushed >> the attached patch, which includes some hints for cfg.mk configuration >> to avoid false positives. Every project seem to have a couple of small >> strings that trigger false positives, but I've not found any least >> common denominator so it seems simplest to silence this per project. >> I've noticed that newer versions of codespell is better than older >> versions at spotting various kind of typos. > > Emacs has the following: > > $ find admin/codespell/ -type f > admin/codespell/README > admin/codespell/codespell.dictionary > admin/codespell/codespell.exclude > admin/codespell/codespell.ignore > admin/codespell/codespell.rc > > Which might help make this syntax-check more customizable. Particularly > the dictionary seems helpful since it can have mappings like > 'file-writeable-p->file-writable-p'.
Thanks for the pointer! I think all of that could be converted into cfg.mk variables and use my 'make syntax-check' codespell rule. But it seems Emacs isn't using 'make syntax-check' from gnulib. I didn't find any configuration in Emacs that seem to be of benefit for my projects, so this re-inforce my feeling that codespell does a fairly good job generally, and any false positives (of which there can be many) are project specific matters. /Simon
signature.asc
Description: PGP signature
