Skip to content
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

Installation Instructions and Code do not match #67

Open
mementum opened this issue Jun 13, 2024 · 2 comments
Open

Installation Instructions and Code do not match #67

mementum opened this issue Jun 13, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@mementum
Copy link

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.

@mementum
Copy link
Author

mementum commented Jun 13, 2024

(lsp-dependency 'grammarly-ls
'(:system "grammarly-ls")
'(:npm :package "@emacs-grammarly/grammarly-languageserver"
:path "grammarly-languageserver"))

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.

@jcs090218
Copy link
Member

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:

~/.emacs.d/.cache/lsp/npm/@emacs-grammarly/grammarly-languageserver/bin/grammarly-languageserver/

@jcs090218 jcs090218 added the bug Something isn't working label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants