Closed runar-rkmedia closed 7 years ago
Upon adding a word or doing a spell check?
On doing a spell-check, with the latex-syntax. Works well with any other syntax.
Do you have any words in the latex dictionary in the settings page?
I confirm this is still an issue, when checking a latex document. I don't understand what you mean by the "latex dictionary in the settings page." I see Plain Text Words, Git Commit Words, AsciiDoc Words, and Markdown Words. Could this be the problem?
Incidentally, my initial bug report indicated I was able to fix the problem on one machine by adding a word with the cursor in a different place. I think this was incorrect, as that machine is also getting the error.
Look in the settings for linter-spell-latex
. It has it's own word list. Probably not the issue, but worth a try.
I do not see the word list there either. in the linter-spell-latex
settings I see only a checkbox for "check settings." On the other hand, in linter-spell-html
I do see the word list box in the settings.
@oscarlevin Something is wrong then. I would check for an update for linter-spell-latex
or uninstall and then reinstall. You might also look in your config settings and manually delete any settings for linter-spell-latex
.
@yitzchak @oscarlevin Same thing happens here. No settings for linter-spell-latex
other than a checkbox for Check comments
. I had a look in the config.cson
located in my .atom
-folder (OSX), and it doesn't list anything for linter-spell-latex
and it lists a ""
-item and two null
-items. I deleded the null
-items, and the settings for TeX, LaTeX and BibTeX word
showed up again. I did a reset of Atom and it works now. Thanks for clearing this up.
Fantastic! I too had a null
in my word list in config.cson
and deleting it and restarting atom did the trick. So glad to have this incredibly useful package back working again. Thanks for the help.
Awesome. Thanks!
I think the problem is not fixed yet. After upgrading to newest versions of both
linter-spell
(0.12.3) andlinter-spell-latex
(0.9.1), I still get the same error as reported.