-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
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
Mark words from built-in dictionary to be flagged #1498
Comments
Turns out I'm using Spell Right instead of Code Spell Checker, but when I googled "spell right vscode remove word from dictionary" it showed this repository as the first result. Thanks for the quick replies. |
There seems to be an issue when part of the word is considered correct. I opened a new issue with the library that does the checking. It is strange that Node isn't already installed on your MBP. Even so, you would need Node and NPM to run the |
I'm going to close this issue, because it is possible to mark words as forbidden except if they are made of parts too short for it to care. I opened a new issue with the library to take care of that. |
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. |
There are a few English words that I do not want to use in my document. It is a formal document, so no contractions like
aren't
,we've
. I also keep mixing uptherefore
("because of") andtherefor
("in front of there"), so I'd like to flagtherefor
.How exactly should I mark words from the built-in dictionary to be flagged?
@Jason3S provides instructions in #117 (comment) (and those same instructions are in the README on the main page) but they do not work for me.
I do not have a
cSpell.json
in the root directory of my project.I have the following
.vscode/cSpell.json
:But
Test aren't test therefor test test
is not flagged.It still is not flagged after adding
to
.vscode/settings.json
. That section is darker than the rest of that file, so I guess that means those settings are ignored.It does flag
tesqfd
, so the extension is active.The text was updated successfully, but these errors were encountered: