Questions: Find definition from libraries installed in container

[emacs-lsp]

Questions: Find definition from libraries installed in container

[yyoncho]

1. I don't have the time to test it now but this should work. Can you describe what exactly happens and add the logs?

2. I run

 xhost +

and then it works.

[ztlevi]

1. I use the repo I attach above and try lsp-jump-to-definition to Deque from from typing import Deque. Then it gives me:

  signal(cl-no-applicable-method (xref-item-location nil))
  cl-no-applicable-method(#s(cl--generic :name xref-item-location :dispatches ((0 #s(cl--generic-generalizer :name eieio--gen$
  apply(cl-no-applicable-method #s(cl--generic :name xref-item-location :dispatches ((0 #s(cl--generic-generalizer :name eiei$
  #f(compiled-function (&rest args) #<bytecode 0x1638e45>)(nil)
  apply(#f(compiled-function (&rest args) #<bytecode 0x1638e45>) nil nil)
  xref-item-location(nil)
  xref--pop-to-location(nil nil)
  xref--show-xrefs(nil nil)
  lsp-show-xrefs(nil nil nil)
  lsp-find-locations("textDocument/definition" nil :display-action nil)
  lsp-find-definition()
  funcall-interactively(lsp-find-definition)
  call-interactively(lsp-find-definition record nil)
  command-execute(lsp-find-definition record)
  execute-extended-command(nil "lsp-find-definition" "lsp-find-def")
  funcall-interactively(execute-extended-command nil "lsp-find-definition" "lsp-find-def")
  call-interactively(execute-extended-command nil nil)
  command-execute(execute-extended-command)

2. How did you run xhost +? I run it on my local shell and run start-emacs.sh, but emacs is still start in terminal.

[zflat]

I have the same question. I try lsp-find-reference and get this error

Warning (lsp-mode): Failed to process xref entry for filename ’/docker:my-docker-langservers:/opt/ros/melodic/include/rosconsole/macros_generated.h’: Method ‘docker’ is not known.

The file path is known and correct within the container. Is there any way to open that file in an emacs buffer? Ideally it would still work with lsp-mode to facilitate further navigation.

If that is not possible, could there be a way to open the buffer using Tramp? In my case, changing the file path from /docker:my-docker-langserver:/opt/... to /ssh:user@host#port:/opt/... would work when the container is running sshd.

[yyoncho]

@zflat can you try installing docker-tramp package?

[zflat]

Yes, that is the fix for handling the xref uri. However, I now have this issue: #29

I have a branch that I am using to test a fix.