Open jefftrull opened 1 year ago
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 :/
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.
I wanted to try Elsa upon the recommendation of a friend so I followed the directions in the README.
(require 'elsa-lsp)
but without it there is noelsa-lsp-register
M-x lsp
fails with the message :but there is no
*lsp-log*
buffer