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 have a python script which allows me to log messages between my lsp client (emacs) and harper. Despite some grammatical mistakes in my test file, "How about this wrong grammars? I are full. We is good.", I'm unable to get diagnostics from Harper. Perhaps there is something simple that someone more familiar with the language server protocol could spot that I'm missing?
I noticed Harper is requesting a workspace/configuration and receiving null, perhaps that has something to do with it?
I think the grammar mistakes in your test file are not supported yet, at least by the default lints enabled. Can you try using "This sentence has grammar errorz, like this this one." as your sample text? You should get back two errors in your diagnostics array, one for a wrong spelling and the other for repeated words, since those are part of the lints enabled by default.
If that doesn't work, you should probably reply to the workspace/configuration request with the lints you want enabled. You can find a list of those here.
Thanks for the reply. I tried including your sentence "This sentence has grammar errorz, like this this one", however, it did not produce any diagnostics. Still working on getting emacs to respond to the workspace/configuration request with the lints I want, and it might take me a while to figure that out, but I can report back when I do.
I have a python script which allows me to log messages between my lsp client (emacs) and harper. Despite some grammatical mistakes in my test file, "How about this wrong grammars? I are full. We is good.", I'm unable to get diagnostics from Harper. Perhaps there is something simple that someone more familiar with the language server protocol could spot that I'm missing?
I noticed Harper is requesting a
workspace/configuration
and receiving null, perhaps that has something to do with it?The text was updated successfully, but these errors were encountered: