Re: Xref completion

[Dmitry Gutov]

On 06.12.2020 10:30, William Xu wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
> > Of course, in the end it depends on each backend to put useful into
> > into summaries. And in the case of etags, that depends on how the
> > definition is written (that the identifier is not alone on its line).
>
> You are right. It is backend specific. So it makes more sense, showing
> the summary by default as you are currently doing.
>
> > > However, at the moment it only shows the same summary info for each
> > > line, which doesn't seem really useful:
> > > /foo.cpp:40:Foo
> > > /foo2.cpp:42:Foo
> >
> > Which backend is this? Also etags?
>
> Eglot with ccls. Sounds like something to improve in either eglot or ccls.

Seems like.

It could also be a limitation of the LSP protocol (looking at 
https://microsoft.github.io/language-server-protocol/specifications/specification-3-15/#location, 
it doesn't have a field for "line text").

But if so, maybe Eglot could visit the files preemptively and extract 
the line contents. Unlike some other operations, there's unlikely to be 
many results in that list, so it shouldn't take long.

It seems to be trying to do something like this already: 
https://github.com/joaotavora/eglot/blob/master/eglot.el#L1927, maybe 
file a report for this particular case.