|
From: | Dmitry Gutov |
Subject: | Re: xref and leaving "temporary" buffers open |
Date: | Sat, 25 Jul 2015 21:30:00 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 |
On 07/25/2015 09:17 PM, martin rudalics wrote:
> ... the distinction of open vs. loaded buffers, ... Please let's try to find a better notation. Both "open" and "loaded" are very confusing. "Fore-/background" buffers, "ex-/implicit" buffers are not good either.
I'm also worried about that.Temporary? Might be not too good for the ones we'll want to keep around indefinitely (although I've yet to see a solid use case for that).
Hidden? I think this term is already in use for the buffers whose names start with a space. At least there's an index entry for "hidden buffers" in the manual, pointing to (elisp)Buffer names.
But there don't seem to be a variable or a function in the core that has both "hidden" and "buffer" in its name, so it could be a good option.
[Prev in Thread] | Current Thread | [Next in Thread] |