Re: threads and kill-buffer

[PJ Weisberg <pj@irregularexpressions.net>]

On Thu, Sep 6, 2012 at 10:52 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 6 Sep 2012 13:49:29 -0700
>> From: PJ Weisberg <pj@irregularexpressions.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, tromey@redhat.com, dmantipov@yandex.ru,
>>       emacs-devel@gnu.org
>>
>> A more interesting question is, what does (get-buffer "*Backtrace*")
>> return in thread A?
>
> As long as A has *Backtrace* as its current-buffer, get-buffer will
> return it.
>
>> I can think of a few commands in Magit that would not behave properly
>> if (get-buffer-create some-string) returned a buffer that couldn't be
>> displayed after the command finished.
>
> What significance is here to the fact that the command finishes?

I was thinking of a command that populates a buffer like
"*magit-log*"(creating it if necessary), and then leaves the user *in*
that buffer so he can interact with it further.

> Anyway, if the buffer in question is killed, but is needed elsewhere
> in Emacs, then that's a bug that needs to be fixed.  We don't need to
> come up with a design that works regardless of bugs, do we?

No, I was just brainstorming things that used to be safe assumptions
(`get-buffer-create' returns a displayable buffer) and now might not
be.

-PJ

Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.