Replies: 6 comments
-
I'm getting a similar problem with rust-analyzer, except I get I've also attempted on a temporary solution, but it doesn't work :( |
Beta Was this translation helpful? Give feedback.
-
Experiencing the exact same thing:
Technically RET is bound to when on the pkg.go.dev link and that is bound to FWIW this is in terminal emacs launched on the remote machine over ssh. OP trick with extracting hidden url |
Beta Was this translation helpful? Give feedback.
-
Same issue here:
I wonder if #865 is somehow related? But the fix for that (PR #866) seems to have been included in eglot 1.17. There's also some mention of an issue on the eldoc side of things, so I'll look a bit at that, too. |
Beta Was this translation helpful? Give feedback.
-
The issue seems to be that markdown-backward-to-link-start uses From an eldoc buffer where
So the links in the eldoc buffer aren't formatted as markdown-mode expects? |
Beta Was this translation helpful? Give feedback.
-
This problem still persists in eglot versioned 1.17. Clicking on the link with mouse or Hitting return in keyboard on the link doesn't work to open the link, but instead, it results in marking the link. And the highlighted text is indeed a link, I can see it by hovering the cursor above it, it shows up the external address. Tested with |
Beta Was this translation helpful? Give feedback.
-
I've come up with a workaround here in combination with @488Ques, it works Note that I only implemented of opening links by the Here's the code: In my init file.
Tweaked for sole use for eldoc-buffer.
|
Beta Was this translation helpful? Give feedback.
-
I'm using the Gopls language server. I have this Golang code
Where I place the point on os.MkdirAll method and M-x eldoc-doc-buffer to see the full documentation
Then I click on the hyperlink
os.MkdirAll on pkg.go.dev
that links to the documentation website of that method, I expect the link to be opened in my web browser but instead only see the messageuser-error: Nothing to follow at point
which is produced bymarkdown-follow-thing-at-point
.I'm not sure if this is intended behavior, a bug or an error on my end.
I made a temporary solution:
Beta Was this translation helpful? Give feedback.
All reactions