[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: threads and kill-buffer
From: |
martin rudalics |
Subject: |
Re: threads and kill-buffer |
Date: |
Thu, 06 Sep 2012 16:41:39 +0200 |
>> >> ... and what if this buffer was meanwhile revived by another thread?
>> >
>> > No other thread can revive that buffer, because the buffer is
>> > invisible to any buffer but those who have it as current.
>> >
>> > The "revived" buffer will be a different buffer, perhaps with the same
>> > name.
>>
>> How could that work with buffers like *Help* or *Backtrace* which are
>> revived all the time? Do you want to clone them?
>
> I don't understand the problem that bothers you. Please elaborate.
Suppose *Backtrace* is current in thread A and gets killed by thread B.
Before making another buffer current for A, a debugger buffer must be
revived for B. Would that be a different buffer from the *Backtrace*
seen in A?
martin
- Re: threads and kill-buffer, (continued)
Re: threads and kill-buffer, SAKURAI Masashi, 2012/09/04
Re: threads and kill-buffer, Dmitry Antipov, 2012/09/05
- Re: threads and kill-buffer, martin rudalics, 2012/09/05
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/05
- Re: threads and kill-buffer, martin rudalics, 2012/09/06
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06
- Re: threads and kill-buffer,
martin rudalics <=
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06
- Re: threads and kill-buffer, martin rudalics, 2012/09/06
- Re: threads and kill-buffer, Stefan Monnier, 2012/09/06
- Re: threads and kill-buffer, martin rudalics, 2012/09/06
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/06
- Re: threads and kill-buffer, martin rudalics, 2012/09/07
- Re: threads and kill-buffer, Stefan Monnier, 2012/09/06
- Re: threads and kill-buffer, martin rudalics, 2012/09/07
- Re: threads and kill-buffer, Stefan Monnier, 2012/09/07