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
;; Example of a minimal configuration
(setq package-enable-at-startup nil
package-archives
'(("melpa"."http://melpa.milkbox.net/packages/")
("gnu"."http://elpa.gnu.org/packages/")))
(require'package)
(package-initialize)
(package-install 'eglot)
(package-install 'elixir-mode)
(package-install 'magit)
(add-to-list 'eglot-server-programs `(elixir-mode . ("/Users/akash/elixir-ls/language_server.sh")))
Steps to reproduce
I think the issue is not specific to any language server, so should be possible to reproduce with any git repo. But mentioning the steps for the sake of completeness
clone and open any elixir git repo
M-x toggle-debug-on-error
create an elixir-mode non-visiting-buffer. By opening any file in different revision from magit stash, diff, log etc
move cursor around to trigger textDocument/signatureHelp
Issue is related to #116. There is a fix for indirect-buffer a1f2033. But in this case this seems to be just a buffer without visiting file.
The text was updated successfully, but these errors were encountered:
I think this is an Eglot bug, but I don't have a good idea for solving it. it never happens to me when I use VC, for example (I don't use Magit). That's because VC uses an actual file to backup the foo-mode buffers it creates.
LSP requires URIs for things. Should we just make up an URI?
Also I can't find the part in your LSP transcript where the textDocument/signatureHelp is issued. I'm looking for the URI of the file-less buffer thing that it presumably invoked didOpen on.
ElixisLS - M-x eglot-events-buffer
Backtrace (mandatory, unless no error message seen or heard):
Minimal configuration (mandatory)
Steps to reproduce
I think the issue is not specific to any language server, so should be possible to reproduce with any git repo. But mentioning the steps for the sake of completeness
textDocument/signatureHelp
Issue is related to #116. There is a fix for indirect-buffer a1f2033. But in this case this seems to be just a buffer without visiting file.
The text was updated successfully, but these errors were encountered: