Open client9 opened 8 years ago
@client9
I'm running this in a pre-commit
hook on a Ruby project and it generally works great! 💯
#!/usr/bin/env bash
if command -v misspell >/dev/null; then
misspell -w -error -source=text {app,config,lib,spec}/**/* 2>/dev/null
fi
Recently it made the correction (false positive)
corrected "Finkelshteyn" to "Finkelstheyn"
Although not in the docs, I ran misspell --help
and saw
-i string
ignore the following corrections, comma separated
and this appears to be a bug in not respecting word boundaries, because it thinks it's a misspelling of they
as htey
misspell -w -error -source=text -i "htey,they" {app,config,lib,spec}/**/* 2>/dev/null
(I read the tests to figure out the ignore syntax)
I can create a new issue, but wasn't sure how you'd like this reported, if it should be separate, or what :)
These are quit unusual spellings or words. They should either be removed from the "known good" list or have the rule removed.