From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lenbok@gmail.com, 75056@debbugs.gnu.org
Subject: bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs
Date: Fri, 27 Dec 2024 09:46:48 +0100 [thread overview]
Message-ID: <m2zfkhfr7r.fsf@gmail.com> (raw)
In-Reply-To: <8634i9y1wa.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 Dec 2024 10:18:45 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Can you explain how the above limitation causes the problem reported
> in this bug? That is, how do child frames trigger the bug? Because
> "normal" frames don't, AFAIU, right? That is, one could have two or
> more client TTY frames on several displays in the same Emacs session,
> without having any of them stop being responsive, right? Also, what
> is the role of vertico-posframe in this scenario?
The hint I see is here
>> If your multi-tty Emacs session seems to be frozen, you
>> probably have a recursive editing session or a pending
>> minibuffer prompt (which is a kind of recursive editing) on
>> another display.
Emacs in our case is kind of frozen, and Vertico is a minibuffer
interaction, where Posframe simply displays the minibuffer differently,
in a child frame.
Not an explanation of course, but it smells a lot like what's happening.
What the real reason behind all this is in the code, and what would need
to be fixed, I can't figure out from notes/multi-tty. Maybe come
combination of open things mentioned there, no idea.
>
> IOW, I don't yet have a clear picture of what happens, although the
> limitations you found in that admin file are known to me. AFAIK, the
> single-kboard situation is still with us, search keyboard.c for
> "single_kboard".
>
>> @Eli: I think we should invoke a multi-tty expert who can tell if what
>> we see here can be kind of expected with the current state of multi-tty or
>> not. And maybe can tell how up-to-date admin/notes/multi-tty is in the
>> first place.
>
> We don't have such an expert on board, sadly, not for a long while.
> We are on our own.
That's indeed more than suboptimal :-(.
next prev parent reply other threads:[~2024-12-27 8:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 5:43 bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs Len Trigg
2024-12-25 11:54 ` Eli Zaretskii
2024-12-25 11:59 ` Gerd Möllmann
2024-12-27 6:04 ` Gerd Möllmann
2024-12-27 8:18 ` Eli Zaretskii
2024-12-27 8:46 ` Gerd Möllmann [this message]
2024-12-27 8:54 ` Eli Zaretskii
2024-12-27 9:04 ` Gerd Möllmann
2024-12-27 12:28 ` Eli Zaretskii
2024-12-27 12:47 ` Gerd Möllmann
2024-12-27 13:02 ` Eli Zaretskii
2024-12-27 13:17 ` Gerd Möllmann
2024-12-27 14:53 ` Eli Zaretskii
2024-12-27 15:56 ` Gerd Möllmann
2024-12-27 18:13 ` Len Trigg
2024-12-27 18:23 ` Len Trigg
2024-12-28 7:52 ` Eli Zaretskii
2024-12-28 19:55 ` Len Trigg
[not found] ` <CAOGVwenNt8a0HmSXTnqu5_FKkxEVMDw0hmak-MLk7Sn6up_wtg@mail.gmail.com>
2024-12-28 7:44 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zfkhfr7r.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75056@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lenbok@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).