Re: threads and kill-buffer

[Tom Tromey <tromey@redhat.com>]

>>>>> "Sam" == Sam Steingold <sds@gnu.org> writes:

Sam> It is a certain way to lose data: imagine thread T1 moving data from
Sam> buffer B1 to buffer B2 and thread T2 killing one of these buffers.

We may eventually need a mechanism to let a thread lock a buffer.  This
kind of thing is harder than it seems.  For example, in your scenario,
you'd presumably want to lock both buffers -- but then you can easily
end up in deadlocks.

Anyway, as Eli said, this particular question is really just about a
single case, of kill-buffer and current_buffer.

Due to the current implementation, right now threads only present a few
problems not already possible with process filters.  For example, your
scenario is possible already.

I'm not trying to minimize the problems you point out; just to defer
them.  The current_buffer thing came up because it is a new problem
arising from the concurrency changes, and one that I think we need to
solve before the branch can be merged.

I'll send a note soon about the other problems in this category.

Tom