all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
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 10:54:19 +0200	[thread overview]
Message-ID: <86wmflwlok.fsf@gnu.org> (raw)
In-Reply-To: <m2zfkhfr7r.fsf@gmail.com> (message from Gerd Möllmann on Fri, 27 Dec 2024 09:46:48 +0100)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: lenbok@gmail.com,  75056@debbugs.gnu.org
> Date: Fri, 27 Dec 2024 09:46:48 +0100
> 
> 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.

Yes, but where is that recursive editing in this scenario?

I guess I'd love to see a C backtrace from that situation.





  reply	other threads:[~2024-12-27  8:54 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
2024-12-27  8:54       ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86wmflwlok.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75056@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --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 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.