[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xref and leaving "temporary" buffers open

From: Dmitry Gutov
Subject: Re: xref and leaving "temporary" buffers open
Date: Sat, 25 Jul 2015 19:28:10 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0

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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]