Re: xref and leaving "temporary" buffers open

[Dmitry Gutov <dgutov@yandex.ru>]

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

>> The question is, should they be killed afterwards.
>
> There are arguments either way, AFAIU, so perhaps make this a
> defcustom.

That's a cop-out answer. Whichever value is the default, will influence 
the implementation (if the buffers are killed right away, they should be 
opened in a special way, otherwise, they must be opened normally, with 
all applicable minor modes).

If the buffers are killed, xref-query-replace will need to account for 
that, and not open too many buffers at the same time. I'm most likely 
missing other issues now.

> Might be reasonable.  Again, if you are in doubt, let a user option
> override that.

Please, let's stop with "implement every behavior a user might want". 
There are better things for a developer to spend time on. Unless a 
particular behavior is requested, a user option is premature.