GNU bug report logs - #76969
kill-buffer fails silently when a thread exists where it's current

Previous Next

Full log

View this message in rfc822 format

From: Dmitry Gutov <dmitry <at> gutov.dev>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: sbaugh <at> janestreet.com, 76969 <at> debbugs.gnu.org
Subject: bug#76969: kill-buffer fails silently when a thread exists where it's current
Date: Fri, 1 Aug 2025 03:01:11 +0300

[Message part 1 (text/plain, inline)]

On 31/07/2025 08:24, Eli Zaretskii wrote:
>> Okay. Do I just copy the argument's description twice? Alternatively,
>> could add references to 'make-thread'.
> Either of these is fine.
> 
>>> Also, these two new primitives should be documented in the ELisp
>>> manual.
>> Are they important enough for the manual? Since 'make-thread' gets the
>> new argument, I'd imagine most users would go through it, or at least
>> learn about "thread disposition" due to that.
> It just takes a sentence or two (and index entries) to mention these.
> You don't have to use the full-fledged @defun thingy.
> 
>> If you're sure, no problem - it's just the section that I'm looking at
>> is called "Basic Thread Functions".
> Right after make-thread, IMO.

Great, updated.

Also added main_thread_p check in thread-set-buffer-disposition.

[thread-buffer-disposition-v2.diff (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.