GNU bug report logs - #75056
31.0.50; tty-child-frames with server / multiple clients possible hangs

Previous Next

Full log

View this message in rfc822 format

From: Len Trigg <lenbok <at> gmail.com>
To: martin rudalics <rudalics <at> gmx.at>
Cc: Gerd Möllmann <gerd.moellmann <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>, 75056 <at> debbugs.gnu.org
Subject: bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs
Date: Thu, 27 Feb 2025 08:28:52 +1300

[Message part 1 (text/plain, inline)]

On Wed, 26 Feb 2025 at 21:45, martin rudalics <rudalics <at> gmx.at> wrote:

>  A child frame is supposed to show a minibuffer unless it is created with
> (minibuffer . nil) or some value specifying a minibuffer on some other
> frame.  How precisely is your child frame created?
>

Sorry, my terminology may not be correct, I meant there are two "input
areas" at once (probably only the second one at the bottom of the frame is
an actual minibuffer?), see picture below:

[image: image.png]

The two input areas is not what we get when the same is invoked in GUI
rather than TTY (and not what the TTY behaviour used to be):

[image: image.png]

(In terms of how it's actually created, I guess that's in one of vertico /
posframe / vertico-posframe).

Cheers,
Len.

[Message part 2 (text/html, inline)]

[image.png (image/png, inline)]

[image.png (image/png, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.