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

LSP instructions fail #223

Open
jefftrull opened this issue Sep 25, 2023 · 2 comments
Open

LSP instructions fail #223

jefftrull opened this issue Sep 25, 2023 · 2 comments

Comments

@jefftrull
Copy link

I wanted to try Elsa upon the recommendation of a friend so I followed the directions in the README.

  1. The instructions do not include (require 'elsa-lsp) but without it there is no elsa-lsp-register
  2. M-x lsp fails with the message :

LSP :: The following servers support current file but do not have automatic installation: elsa
You may find the installation instructions at https://emacs-lsp.github.io/lsp-mode/page/languages.
(If you have already installed the server check lsp-log)

but there is no *lsp-log* buffer

@Fuco1
Copy link
Member

Fuco1 commented Oct 5, 2023

You can also try to run eask exec elsa-lsp (or cask ...) in the terminal to see if it errors out on anything.

lsp-log comes from lsp mode so it should definitely pop up if there's some problem. Does it say in the minibuffer that the LSP server errored and whether you want to restart it? That might indicate some problem with Elsa itself.

I'm surprised someone even recommended this :D It's still very academical project and things often break and in general are not useful enough because we still lack the built-ins coverage (currently it's maybe at 10-15% at best). I've been working on generics very hard during April but since then almost nothing. It's the one big feature before a "1.0" release without which the usefulness is quite limited :/

@jefftrull
Copy link
Author

Unfortunately I'm unable to even get that far anymore... (require 'elsa-lsp) dies with a backtrace on a (void-variable elsa-explainer-message).

The advantage of using this method with Elsa is that I don't have CI set up at the moment, but would still like to learn what issues there might be with my code. lsp (which I use all the time) seemed like a convenient way to check out your package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants