emacs-devel
[Top][All Lists]
Advanced

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

Re: Some experience with the igc branch


From: Paul Eggert
Subject: Re: Some experience with the igc branch
Date: Sun, 29 Dec 2024 11:30:22 -0800
User-agent: Mozilla Thunderbird

On 12/29/24 11:20, Eli Zaretskii wrote:
if a non-main thread's Lisp function keeps running forever,
never calling any primitives that release the lock, that thread will
run forever, and the main thread will never get a chance.  Lisp
programs that cause this are considered buggy, of course.

I don't see this issue documented explicitly in doc/elisp/threads.texi.
Should it be?
I will have an opinion when I better understand what "it" is in this
case.  I hope this is just a misunderstanding.

It's the issue summarized in your paragraph that I quoted above, along with its consequences, which are obvious to someone who knows how Emacs Lisp threads work but not so obvious to newcomers who may have several notions of "threads" rattling around in their heads.

It's not just that the main thread never gets a chance: it's that signals are effectively ignored.

Does the same thing happen with C-g? If so, I'd think that should also be documented in threads.texi.



reply via email to

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