Re: xref and leaving "temporary" buffers open

[Dmitry Gutov <dgutov@yandex.ru>]

On 07/25/2015 07:15 PM, Eli Zaretskii wrote:

> You could detect this using buffer-modified-tick, no?  You could also
> refrain from killing any of these buffers displayed in some window, or
> present in the relevant history lists.

The tick doesn't change if the user hasn't modified the contents. And if 
the buffer is not visible just now, that doesn't mean that it's 
unwanted. Both useful heuristics, but still less than ideal, IMO.

> That's not what I meant.  What I meant was that the manuals are not
> available once the command finishes, although its quite clear the
> command had to visit each and every one of them.

Yes, both xref-collect-references and xref-collect-matches delete the 
newly opened buffers in the end as well. Unfortunately, an average 
xref-find-references call takes a longer than info-apropos, IME, in 
large part because it has to (re)open the files.