-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Q: Is it possible to support per-language prefixes -a.k.a. do not flag words with prefixes like "un" or "pre" or "co"? #5286
Q: Is it possible to support per-language prefixes -a.k.a. do not flag words with prefixes like "un" or "pre" or "co"? #5286
Comments
Thank you for the suggestion. Doing what you suggest is not technically hard, but it is hard to ensure it is correct. For example, The dictionaries are pretty extensive. They consist of hundreds of thousands or even millions of words. Very large dictionaries are not an issue. The time to look up a word is based upon the length of a word, not the size of the dictionary. So adding |
One more: |
Please feel free to create a PR to add |
Fixes streetsidesoftware/cspell#5286 CSpell has been nagging about these words found in the Backdrop CMS codebase.
I just filed a PR that adds some words that start with the "un" prefix: streetsidesoftware/cspell-dicts#3129 Also adds |
Thank you for picking that one up. :) |
Closes #3129 fixes: streetsidesoftware/cspell#5286
The following are some examples that CSpell flags as wrong.
instantiatable
is flagged, but it is a valid word: https://en.wiktionary.org/wiki/instantiatable)Words like the above make sense in coding, although there may not be officially included in any dictionary, so they should not be flagged. Instead of adding individual such words in the various dictionaries, which is impractical and kinda silly, I believe that cspell should follow the following logic:
I believe that there should be a way to define a list of such prefixes (and perhaps suffixes as well?), and that this configuration should be per language.
The text was updated successfully, but these errors were encountered: