bug#81596: 30.2; Eldoc: "Nothing to follow at point" despite text appearing like a link (underlined, hoverable, with URL tooltip)
Rahul Martim Juliato <[email protected]>
| Newsgroups | gmane.emacs.bugs |
|---|---|
| Message-ID | <[email protected]> |
Stéphane Marks <[email protected]> writes: > On Fri, Aug 14, 2026 at 11:29 AM Sean Whitton <[email protected]> > wrote: > >> Ramón Cahenzli via "Bug reports for GNU Emacs, the Swiss army knife of >> text editors" [11/Aug 9:01am +02] wrote: >> > When a language server emits documentation in Markdown format, eldoc >> > attempts to render this in its buffer, including making links >> > clickable/followable. Most of those seem to work, but some don't. In >> > such cases, the text is displayed as if it were a link (it's underlined >> > and reacts to hover) but following it doesn't work: >> > >> > markdown-follow-link-at-point: Point is not at a Markdown link or URL >> > markdown-follow-thing-at-point: Nothing to follow at point >> > >> > Function names mentioned inside help text in elixir-ls show this >> > behavior, for example. The URL in the tooltip points to documentation >> > for that specific function on Hexdocs, but the link doesn't work when >> > clicked. >> > >> > In both working and non-working cases, the URL is in the "help-echo" >> > text property. It might be a bug because it feels misleading when the >> > text looks and behaves like a link in the UI but can't be >> clicked/browsed. >> > >> > Some other editors, e.g. Kate and Codium, seem to have decided that such >> > text shouldn't be a link at all and just display it in a monospaced font >> > with different background colors. But it feels like the more useful >> > behavior for the user would be to let them follow the link to the >> > documentation since it's already there. >> >> Thanks, adding João. >> > > + Rahul in case we can accommodate something easily (and if appropriate) in > markdown-ts-mode. > > It would be nice to know how to reproduce such a markdown input as the > report excluded a recipe that I could see. Thanks for adding me Stéphane. Indeed, this is something we could help solve in `markdown-ts-mode` given more information and a reproducible case. -- Rahul Martim Juliato