Re: Adding support for xref jumping to headers/interfaces

[João Távora]

On Mon, Nov 27, 2023 at 5:05 PM Dmitry Gutov <dmitry@gutov.dev> wrote:

> > What same implementation?? They only common part is is literally just
> > the string "xref-define-finder", the opening and the closing parenthesis.
> > Then comes the backend specifics.  A JSONRPC-based transport with a specific
> > protocol, an HTTP transport with another protocol, a ask the oracle of 
> > Delphos
> > protocol, etc.
> >
> > Realistically, most people will be using Eglot anyway, so the existing
> > eglot-find-* commands are what they're going to see and use.
>
> So that's what your argument comes down to in practical sense -- keep
> the commands in Eglot, and not worry much about other Xref backends.
> Whether they are alternative LSP clients or not.

No, of course not.  And frankly it's a bit silly to try to
caricaturize my position with this strawman, given how much of
my text you've read.  I provided ample support for other backends
and  I myself want to write such a non-Eglot backend for SLY
Common Lisp support.

João