[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65837: 30.0.50; Debugger in non-main threads
From: |
Helmut Eller |
Subject: |
bug#65837: 30.0.50; Debugger in non-main threads |
Date: |
Sat, 09 Sep 2023 17:35:22 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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
- bug#65837: 30.0.50; Debugger in non-main threads, Helmut Eller, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Eli Zaretskii, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads,
Helmut Eller <=
- bug#65837: 30.0.50; Debugger in non-main threads, Eli Zaretskii, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Helmut Eller, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Eli Zaretskii, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Helmut Eller, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Eli Zaretskii, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Helmut Eller, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Eli Zaretskii, 2023/09/09
- bug#65837: 30.0.50; Debugger in non-main threads, Helmut Eller, 2023/09/09