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
The code is looking for grammarly-ls on the PATH. But the binary which is installed by npm is grammarly-languageserver. This means that if the binary is installed manually as indicated by the general lsp-mode instructions, the binary will never be found
If looking for the binary of the auto-installed it will also fail if running for example under cygwin, because npm will install the binary directly under the {prefix}, but the entire lsp-mode chain is looking for the binary under {prefix}/bin
Note: it only runs for a few seconds and then exists ... but this is for another repository.
The text was updated successfully, but these errors were encountered:
Notice the :system grammarly-ls, which is what is being sought system-wide (using the PATH), but there is no such binary/script in the @emacs-grammarly/grammarly-languageserver package.
The code is looking for grammarly-ls on the PATH. But the binary which is installed by npm is grammarly-languageserver. This means that if the binary is installed manually as indicated by the general lsp-mode instructions, the binary will never be found
Yeah, you are right. It's been a while, so I don't remember why I coded the binary name like this. 😅
If looking for the binary of the auto-installed it will also fail if running for example under cygwin, because npm will install the binary directly under the {prefix}, but the entire lsp-mode chain is looking for the binary under {prefix}/bin
I'm unsure about this since I am unfamiliar with Cygwin's settings. This is the Grammarly language server installed path look like on macOS:
The code is looking for
grammarly-ls
on the PATH. But the binary which is installed by npm isgrammarly-languageserver
. This means that if the binary is installed manually as indicated by the generallsp-mode
instructions, the binary will never be foundIf looking for the binary of the auto-installed it will also fail if running for example under
cygwin
, because npm will install the binary directly under the{prefix}
, but the entirelsp-mode
chain is looking for the binary under{prefix}/bin
Note: it only runs for a few seconds and then exists ... but this is for another repository.
The text was updated successfully, but these errors were encountered: