[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: Tue, 28 Jul 2015 22:13:11 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0

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.

reply via email to

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