Re: Adding support for xref jumping to headers/interfaces

[Dmitry Gutov]

On 11/11/2023 14:39, Spencer Baugh wrote:
> Dmitry Gutov<dmitry@gutov.dev>  writes:
> > On 09/11/2023 19:07, Spencer Baugh wrote:
> > > Custom kinds would still require you to type in the kind symbol.  (Or a
> > > backend or mode can make a "quick-access" command specific to that kind,
> > > if they want.)
> > If we leave all the UI decisions to the backends (both extra commands
> > and the dispatch which kind to use in the "unifying" command as well),
> > then there might be little point in adding extra infrastructure to
> > xref.el itself.
> >
> > xref-show-xrefs is a public function, FETCHER just needs to return a
> > list of xrefs, the same data that backend functions like
> > xref-backend-definitions return.
> I think we plausibly leave UI decisions to the*major-modes*.

I don't think so: major modes provide information to common facilities 
(other examples are font-lock or indent-line-function or syntax tables), 
and then the common code uses that information in the same fashion (e.g. 
obeys font-lock-maximum-decoration).