You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I go back and forth on if this is a good idea or not.
I find CSpell useful while coding, since it can work on both normal prose (.md, .txt, etc) and on code files (.R, etc) while being pretty good about dealing with coding conventions, like snake case.
The concept is simple, split camelCase and snake_case words before checking them against a list of known words.
which is great, but leads to my single biggest frustration when dealing with CSpell: maintaining the custom word list. Overall, it's not that difficult, since CSpell traverses up the directory tree until to find custom dictionaries, which means keeping a wordlist in the repo root, and updating it when new words are added to the repo.
I don't have any benchmark as to how any of our repos fare against the standard dictionaries
The text was updated successfully, but these errors were encountered:
Ooof I would be very hesitant to enforce this at all. I think people should use if they want, but I had CSpell enforced in my local neovim config for a bit and hated it.
I spent 99% of my time adding things to the exception list and I eventually just removed it
Recognizing that that may have been an issue with HOW i configured it
I go back and forth on if this is a good idea or not.
I find
CSpell
useful while coding, since it can work on both normal prose (.md
,.txt
, etc) and on code files (.R
, etc) while being pretty good about dealing with coding conventions, like snake case.https://cspell.org/docs/how-it-works/ lays out:
which is great, but leads to my single biggest frustration when dealing with CSpell: maintaining the custom word list. Overall, it's not that difficult, since
CSpell
traverses up the directory tree until to find custom dictionaries, which means keeping a wordlist in the repo root, and updating it when new words are added to the repo.I don't have any benchmark as to how any of our repos fare against the standard dictionaries
The text was updated successfully, but these errors were encountered: