I see, if there was generic support for eglot-mode, it would work for both languages and probably many more.
Robert Weiner <rsw...@gmail.com> writes: > Hi Marc: > > There presently is no Hyperbole support for either language. Maybe if > we generalize the language-specific handling, we’ll add some. > > -- rsw > >> On Apr 10, 2024, at 9:15 AM, Marc Coquand <marc@mccd.space> wrote: >> >> >> Hi! >> >> Thanks for the rapid response. >> >> So the languages where it did not work are Typescript >> and OCaml, both running in eglot mode. >> >> Sincerely, >> Marc >> >> Robert Weiner <r...@gnu.org> writes: >> >>> Hi Marc: >>> >>> In general, Hyperbole will use the current xref backend for >>> definition lookup, but this is language-specific as other >>> methods have been preferred in the past. For example, in Python, the jedi >>> language server traditionally was >>> preferred over xref (often TAGS files). We are redoing the Python support >>> now to allow for Eglot or other xref >>> backends. What language(s) are you using where Hyperbole did not invoke >>> your xref backend? >>> >>> -- rsw >>> >>> On Tue, Apr 9, 2024 at 4:43 PM Marc Coquand <marc@mccd.space> wrote: >>> >>> Heya, >>> >>> With embark, currently embark-dwim figures out that if I select a >>> function with eglot mode running, I want to go to definition. >>> >>> Is there something similar available for hyperbole that can be setup? >>> I'd love it if the M-Ret would open the reference of the function at point >>> (xref-find-definitions) or otherwise attempt >>> eldoc-documentation-at-point. >>> >>> Thanks in advance for all help. >>> Marc >>
