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 use the VS-Code plug-In (v13.1.0) to spell check a LaTeX file. For some reason the plug-in does not seem to find any spelling mistakes. For example, if I type: "Why don't you find a obvious mistak." it tells me that "a" should be "an" and that the period should be a question mark, but it does not flag the fact that I misspelled "mistake". When I first started using the plug-in, spell checking worked and I suspect, that I might have disabled spell checking at some point, when I told it to ignore a specific error. I tried reinstalling the plug in multiple times and I checkt the settings in the setup.json file but I can't find the problem.
If you need more specific information please let me know, I am pretty new to all of this. Thanks in advance for your help!
The text was updated successfully, but these errors were encountered:
I found the problem. The rules I deactivated were not defined in the setup.json but in an external file in the .vscode folder. Once I deleted this file and reinstalled LTeX, it worked again.
I use the VS-Code plug-In (v13.1.0) to spell check a LaTeX file. For some reason the plug-in does not seem to find any spelling mistakes. For example, if I type: "Why don't you find a obvious mistak." it tells me that "a" should be "an" and that the period should be a question mark, but it does not flag the fact that I misspelled "mistake". When I first started using the plug-in, spell checking worked and I suspect, that I might have disabled spell checking at some point, when I told it to ignore a specific error. I tried reinstalling the plug in multiple times and I checkt the settings in the setup.json file but I can't find the problem.
If you need more specific information please let me know, I am pretty new to all of this. Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: