[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: threads and kill-buffer

From: Dmitry Antipov
Subject: Re: threads and kill-buffer
Date: Wed, 05 Sep 2012 08:34:48 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120824 Thunderbird/15.0

On 09/05/2012 12:36 AM, Tom Tromey wrote:

Suppose thread T has buffer B as its current buffer, and then some other
thread evaluates (kill-buffer B).  What should happen in thread T?

(assuming other thread is P) T should continue editing, but P marks B
as no longer available to set as current (so B can't be used as current
in another thread); when T switches from B to another buffer, B is really

Another problem with this approach is just that it is hard to implement.
I see 1085 references to 'current_buffer' in the tree, and presumably
I'd have to examine each one...

Why not just define current_buffer to something like:

#define current_buffer current_thread ()->data->current_buffer

and see what happens?


reply via email to

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