-
Notifications
You must be signed in to change notification settings - Fork 61
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
Spell check enabled but not working #344
Comments
I see the same on Ubuntu 18, Vim 8 |
Same issue but i notices spelling only stops working if i set a custom |
I had the same issue. After troubleshooting I found that the syntax file for java located at Removing The current setting can be verified by typing |
Great tip @NicolajNiels1. That might explain why I've never been able to replicate various reports like this (I don't have Java enabled as a possible embedded language) and why it keeps coming up. It might not be just Java either, perhaps there are other languages that trip people up. I wonder if this is something we can mitigate by saving / restoring the setting after loaded embedded syntaxes. I think we do that already for some other settings. |
I checked and the my problems is traceable to |
Thanks @meck, I think we're on to something. I'm pretty sure there is a way we can block this change. |
Running groovy.vim:226: syntax spell default " added by Bram
java.vim:161: syntax spell default
papp.vim:29: syntax spell default " added by Bram
spyce.vim:22:syntax spell default " added by Bram (Of course this is dependent on which vim distribution you are using. I am using |
Removed those two as they were causing spell check to fail on markdown files. More details here: vim-pandoc/vim-pandoc-syntax#344. Possible workaround could include ensuring that `:syntax spell toplevel` is set when markdown file is loaded.
I have spell check enabled for markdown documents. For some reason, with this plugin enabled, no spelling mistakes are detected. If I disable this plugin, the errors are detected.
I'm using Neovim 0.5 on Windows 10.
The text was updated successfully, but these errors were encountered: