[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 15:57:59 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0

On 07/27/2015 07:02 PM, martin rudalics wrote:

A buffer is atomically dead when its name is set to nil.  So
conceptually there should never be any problems.  Yet, there are all
those checks whether a buffer has recursively become dead in
`kill-buffer' which always keep me wondering ...

We'll see, I suppose.

 > By the way, I wonder if we're going to discourage, or somehow
 > specially handle, calling find-file-noselect with RAWFILE t.

This is one of the problems I see.  Another issue is that of name
management.  Would a hidden buffer's name be uniquified?

Probably. Different buffers with the same name are not allowed, right?

Something else might be worth doing is emulating semantic-find-file-noselect in some generic way.

It's hard to draw a line, but maybe we don't need to know the VC status of any hidden buffer, or enable any (?) of the minor modes in it. But the point is to speed up opening the buffers.

reply via email to

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