Re: xref and leaving "temporary" buffers open

[Dmitry Gutov]

On 07/28/2015 06:40 PM, martin rudalics wrote:

> In this case uniquify will rename the first buffer to bar<foo> and name
> the second buffer bar<bar>.  The user will notice that her buffer has
> been renamed although she has no idea that a buffer bar<bar> exists.

Yes, it looks like a problem. uniquify is a prime candidate for delayed 
enabling of features. Ideally, we'd avoid uniquifying a hidden buffer, 
but perform uniquification as soon as it's no longer hidden.

>  > I suppose. That's the same issue I mentioned WRT
> find-buffer-visiting, right?
>
> Probably.  I forgot.  How many files do we need to make this investment
> pay off?

Not too many. The exact numbers depend on each file. But e.g.

(with-current-buffer (find-file-noselect "src/xdisp.c")
  (syntax-propertize (point-max)))

takes whooping 400ms the first time.