[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: threads and kill-buffer
From: |
Eli Zaretskii |
Subject: |
Re: threads and kill-buffer |
Date: |
Wed, 05 Sep 2012 22:50:25 +0300 |
> From: Tom Tromey <address@hidden>
> Cc: Eli Zaretskii <address@hidden>, address@hidden
> Date: Wed, 05 Sep 2012 13:10:00 -0600
>
> >> I have been thinking about it and the only issue I see is that,
> >> since it introduces a new buffer state,
>
> Stephen> Not one that's visible to Lisp. Why would it be?
>
> It is visible because in thread T, the buffer is still the current
> buffer, but is semi-live. On the trunk (buffer-live-p (current-buffer))
> can never be nil, but under this proposed change, it could be.
I think we should try to arrange things in such a way that for a
thread that has this buffer as current everything looks and feels as
if the buffer were not killed at all.
Re: threads and kill-buffer, Tom Tromey, 2012/09/05
- Re: threads and kill-buffer, Stephen J. Turnbull, 2012/09/05
- Re: threads and kill-buffer, Tom Tromey, 2012/09/05
- Re: threads and kill-buffer,
Eli Zaretskii <=
- Re: threads and kill-buffer, Stephen J. Turnbull, 2012/09/05
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06
- Re: threads and kill-buffer, Stephen J. Turnbull, 2012/09/06
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06
- Re: threads and kill-buffer, Stephen J. Turnbull, 2012/09/06
Re: threads and kill-buffer, Stephen J. Turnbull, 2012/09/05
Re: threads and kill-buffer, Eli Zaretskii, 2012/09/05
Re: threads and kill-buffer, Eli Zaretskii, 2012/09/05
Re: threads and kill-buffer, Stefan Monnier, 2012/09/05
Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06