[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 05:53:56 +0300 |
> From: Tom Tromey <address@hidden>
> Date: Tue, 04 Sep 2012 14:36:22 -0600
>
> One idea here would be to make various operations on buffers throw an
> exception if the killed buffer were used. For example, "insert" would
> do this.
>
> One problem with this approach is that this may mean that 'let' could
> now throw a "killed-buffer" exception in some cases. This seems
> moderately surprising.
>
> 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...
>
>
> Yet another idea is to make kill-buffer refuse to do this.
How about letting kill-buffer succeed, but delay the actual deletion
of the buffer until no thread has it as current, like what Posix
filesystems do with file deletion?
- threads and kill-buffer, Tom Tromey, 2012/09/04
- Re: threads and kill-buffer, Lars Ingebrigtsen, 2012/09/04
- Re: threads and kill-buffer, Paul Eggert, 2012/09/04
- Re: threads and kill-buffer,
Eli Zaretskii <=
- Re: threads and kill-buffer, Sam Steingold, 2012/09/05
- Re: threads and kill-buffer, Eli Zaretskii, 2012/09/05
- Re: threads and kill-buffer, Sam Steingold, 2012/09/05
- Re: threads and kill-buffer, Eli Zaretskii, 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, Stephen J. Turnbull, 2012/09/05
- Re: threads and kill-buffer, Tom Tromey, 2012/09/05
- Re: threads and kill-buffer, Stephen J. Turnbull, 2012/09/06
- Re: threads and kill-buffer, Stefan Monnier, 2012/09/05