From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs Date: Fri, 27 Dec 2024 14:28:59 +0200 Message-ID: <86v7v5wbqs.fsf@gnu.org> References: <8634i9y1wa.fsf@gnu.org> <86wmflwlok.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29509"; mail-complaints-to="usenet@ciao.gmane.io" Cc: lenbok@gmail.com, 75056@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Dec 27 13:30:28 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tR9U3-0007Qn-VA for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 27 Dec 2024 13:30:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tR9Tr-0002YV-IC; Fri, 27 Dec 2024 07:30:16 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tR9Ti-0002Vj-9L for bug-gnu-emacs@gnu.org; Fri, 27 Dec 2024 07:30:10 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tR9Tf-0007oo-Ns for bug-gnu-emacs@gnu.org; Fri, 27 Dec 2024 07:30:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-version:References:In-Reply-To:From:Date:To:Subject; bh=sUe4hiEfnXLPl/uydM3nyGpyOogHDHDUlon+0advmlU=; b=ThL5jXXbWJHZXagnRAu3nZ6xtE/sNg6DZtZTh70HfT+AkoUddVv+Mc5XlDZ9hmG0fao6napE92Iu3Awz1BJa/xcrCzjvB3sO4ntTcFZQrsboQyj7ZzgS0GaT9w9dEyktENzhUd2BqTHsrC3nRTxnfRlWrHv2kQ0t5HH3ROLjXpvm78DtSJ955VVI5ZZeVu0oNFVAnJuMS5XV2vnFSosWGFu0zaGibar9JyiHEATGIZcrLkqBQUOnRuyfA5Rxqf5jrGo0RxpUTnaw2rZuv4p4xfXkyWowdkr9Kj+VJdWAUE+R0gIQoSJqJRpEqDT2ljkVti9cV726a8Wo5VaunL5YTQ==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tR9Te-0006Ar-VX for bug-gnu-emacs@gnu.org; Fri, 27 Dec 2024 07:30:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 27 Dec 2024 12:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75056 X-GNU-PR-Package: emacs Original-Received: via spool by 75056-submit@debbugs.gnu.org id=B75056.173530256123607 (code B ref 75056); Fri, 27 Dec 2024 12:30:02 +0000 Original-Received: (at 75056) by debbugs.gnu.org; 27 Dec 2024 12:29:21 +0000 Original-Received: from localhost ([127.0.0.1]:44973 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tR9Sy-00068h-IW for submit@debbugs.gnu.org; Fri, 27 Dec 2024 07:29:20 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33778) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tR9Sw-00068N-6c for 75056@debbugs.gnu.org; Fri, 27 Dec 2024 07:29:19 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tR9Sq-0007eZ-SH; Fri, 27 Dec 2024 07:29:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=sUe4hiEfnXLPl/uydM3nyGpyOogHDHDUlon+0advmlU=; b=PKvV1yLyg0DSt/JfTZsh oT98a/rHCfSb4nVBAFlOsCRN9uAvkEiVOCbAjrr/40T5Css8DXoQmLHsfULMZHpT8XvxlQQMtuoXS gN3pj/emTYOxEadqnCfKRO/uwMFbQ7Gf4QnhgIPJWnERipp2U2bCNriTLzczHDVEBWSG/HdT4n5Fc WCIgu9Y1fj9SFas4MCgePA8KA+DwYz2d/talqaTmOhOEG6+hA5TFdDpLw/DYeT3czX75oT5iQD60a 4gY2XXTrOXQ0g2n10y0OR3XhCSh/Tg9O90f6hcmXlsw1/F7USkXPS3fiyD+gyuLWtay2oYsL+j7Bp 4zVijSGg0s240A==; In-Reply-To: (message from Gerd =?UTF-8?Q?M=C3=B6llmann?= on Fri, 27 Dec 2024 10:04:29 +0100) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:297821 Archived-At: > From: Gerd Möllmann > Cc: lenbok@gmail.com, 75056@debbugs.gnu.org > Date: Fri, 27 Dec 2024 10:04:29 +0100 > > Eli Zaretskii writes: > > >> From: Gerd Möllmann > >> Cc: lenbok@gmail.com, 75056@debbugs.gnu.org > >> Date: Fri, 27 Dec 2024 09:46:48 +0100 > >> > >> Eli Zaretskii 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? > > We're switching frames while being in the minibuffer in the other frame. > > > I guess I'd love to see a C backtrace from that situation. > > Too difficult for me. Emacs is not frozen in the sense that it is > completely stuck somewhere. For example, C-x C-c apparently always > works. C-g seems to work sometimes too, sometimes not. It's more like > the keyboard input doesn't land where it is supposed to. Or something > like that. Then why is this a bug? When a frame is in a minibuffer, it means Emacs asks the user about something, and in that situation, the user must respond to the prompt, or exit the minibuffer in some other way. That's normal in my book. What am I missing?