We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flagWords
I switched to Spell Checker because Spell Right cannot flag words from the dictionary. Spell Checker does not flag everything here:
I would expect it to flag everything except Test and test. Does it split on ' and not flag words shorted than 2 letters?
Test
test
'
My .vscode/cSpell.json:
.vscode/cSpell.json
{ "version": "0.2", "language": "en", "words": [ <omitted> ], "flagWords": [ <omitted> "therefor", <omitted> "they'd", "they'll", "they're", "they've", <omitted> "therefor" ] }
MBP:dir user$ npx cspell trace therefor bash: npx: command not found
Would this work even if I did install nodeJS? Where does it get the cspell package?
Originally posted by @MeAmAnUsername in streetsidesoftware/vscode-spell-checker#1498 (comment)
The text was updated successfully, but these errors were encountered:
Related to #1895
Sorry, something went wrong.
dev: Catch forbidden whole words
c437e2b
Fix #1953
dev: Catch forbidden whole words (#2000)
b76fd12
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Successfully merging a pull request may close this issue.
I switched to Spell Checker because Spell Right cannot flag words from the dictionary.
Spell Checker does not flag everything here:
I would expect it to flag everything except
Test
andtest
. Does it split on'
and not flag words shorted than 2 letters?My
.vscode/cSpell.json
:Would this work even if I did install nodeJS? Where does it get the cspell package?
Originally posted by @MeAmAnUsername in streetsidesoftware/vscode-spell-checker#1498 (comment)
The text was updated successfully, but these errors were encountered: