From: Helmut Eller <eller.helmut@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65837@debbugs.gnu.org
Subject: bug#65837: 30.0.50; Debugger in non-main threads
Date: Sat, 09 Sep 2023 17:35:22 +0200 [thread overview]
Message-ID: <m2pm2r2wcl.fsf@gmail.com> (raw)
In-Reply-To: <83bkebvbsj.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Sep 2023 14:14:20 +0300")
On Sat, Sep 09 2023, Eli Zaretskii wrote:
> AFAIR, it is not trivial to improve
> the thread error handling significantly, but patches are welcome, of
> course.
Is there a design/plan for how recursive-edit is supposed to work in
non-main threads?
E.g. some options that come to mind:
1) It should be allowed without restriction (what currently seems to be
happening).
2) There should be some locking/multiplexing scheme so that only some
"foreground thread" is allowed to read events from the keyboard.
3) Only the main thread is allowed to call recursive-edit; all other
threads have to communicate with the main thread in some way. (Maybe
there should be one thread per terminal that runs a command loop, but
that's an exotic detail.)
Helmut
next prev parent reply other threads:[~2023-09-09 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 9:15 bug#65837: 30.0.50; Debugger in non-main threads Helmut Eller
2023-09-09 11:14 ` Eli Zaretskii
2023-09-09 15:35 ` Helmut Eller [this message]
2023-09-09 15:57 ` Eli Zaretskii
2023-09-09 16:23 ` Helmut Eller
2023-09-09 16:46 ` Eli Zaretskii
2023-09-09 17:24 ` Helmut Eller
2023-09-09 17:37 ` Eli Zaretskii
2023-09-09 18:29 ` Helmut Eller
2023-09-09 18:34 ` Eli Zaretskii
2023-09-09 18:50 ` Helmut Eller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pm2r2wcl.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=65837@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.