Re: Adding support for xref jumping to headers/interfaces

[Dmitry Gutov]

On 27/11/2023 16:49, João Távora wrote:
> On Mon, Nov 27, 2023 at 2:43 PM Dmitry Gutov <dmitry@gutov.dev> wrote:
>
> > (that's what the completing-read approach is for), and whenever we find
> > out that particular kinds get supported by many backends (or by most of
> > the available/popular ones), we could "pull them into the core", adding
> > a global command with one binding which would work across languages.
>
> Alright, so since this is contentious (who else but you is pushing
> this idea?)

Indeed, I wonder if nobody else is interested in having the additional 
commands have pre-defined bindings, or having the same bindings across 
languages.

> what about we start with 0 in xref.el.  We can always
> add to 0, no problem, but taking away  from some other number
> isn't so easy.

We could indeed start with 0, but then I already see the same set of 
extra commands supported in Eglot, Elisp, lsp-mode

> >   and to allow frictionless extensions for special capabilities.
>
> As to frictionless extension, the macro I proposed already
> xref-define-finder seems the easiest way by far.

Sorry, I can't find it.

But the definition of xref-find-declarations takes about 3 lines. There 
is not much potential for making it even shorter.