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 10:18:45 +0200 Message-ID: <8634i9y1wa.fsf@gnu.org> References: 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="39352"; 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 09:19:18 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 1tR5Yz-000A3R-VE for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 27 Dec 2024 09:19:18 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tR5Yl-0000nK-PD; Fri, 27 Dec 2024 03:19:03 -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 1tR5Yk-0000n5-OL for bug-gnu-emacs@gnu.org; Fri, 27 Dec 2024 03:19:02 -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 1tR5Yk-0003ms-Fg for bug-gnu-emacs@gnu.org; Fri, 27 Dec 2024 03:19:02 -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=e5jCBi2ufsQ4TnHUwiPWGQH/i2dNdQlqfb12KY1qEh4=; b=p4rtooZ3YWpT6IFCRIDLY2/kYMcMXAeul9tAeitfY5AJA7864PrtwIBsqDY0GROcOzNaQ1dfGlbNB6fEPeGqFejGorDrmebgWCrXAc5hxoKKZq86qLIa5eh0fq9DQ/73GoqCBKU3DxD18iKze/X5y4bLLnshOzN/81jkZGUGI7Xx20Lld6C3Ii9q95yQXiMFnKLpPQaRrtQd+hsfeOUAeucWLaSPZwj6Av6VBwaMbXBbMMtOBoiWqU8p5j59SC6i+fjGsRH++NB47pUwTL26Zs28i/tg2VMRB8XmhSxMGTpL3ATaKtVvW+dF8z2cv0J0zMCqgb5gsigNeBYRnySA8A==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tR5Yk-0002f6-9M for bug-gnu-emacs@gnu.org; Fri, 27 Dec 2024 03:19: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 08:19: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.173528753910224 (code B ref 75056); Fri, 27 Dec 2024 08:19:02 +0000 Original-Received: (at 75056) by debbugs.gnu.org; 27 Dec 2024 08:18:59 +0000 Original-Received: from localhost ([127.0.0.1]:44592 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tR5Yh-0002ep-3V for submit@debbugs.gnu.org; Fri, 27 Dec 2024 03:18:59 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51464) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tR5Ya-0002eM-Dl for 75056@debbugs.gnu.org; Fri, 27 Dec 2024 03:18:56 -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 1tR5YU-0003ld-TX; Fri, 27 Dec 2024 03:18:46 -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=e5jCBi2ufsQ4TnHUwiPWGQH/i2dNdQlqfb12KY1qEh4=; b=M5QO4WmzFVsB7n+Du4EB osFLZcouzWm1wysVfWooa5GKfZ4HquzWAQZKDvgPxyZAJDYBGTeTQYBYsdc2gE7XKWHm8tA5Dfgmk F1iL9MeLGssvA+VmImk4EKlgVxDHqhx5ZPHe5fGVSsh1mDRfJPsqEnC0LgX4gxNgtavroP5It+Tjy gxrfyJ8akfeNt2oisbHRofGh4Ej9YFMbX4UaU8OQ+A8ulE1hueHCNVWm5sj3ZMCu4yo/X9zh7Re/r sxOptvofHv9IgwINS7a7uiYJKKWFmUSbgj9qOQct/9rAjOGdItspHMdmRsnBD70FLoWFBAti38s8u hhNlg4czasXHBQ==; In-Reply-To: (message from Gerd =?UTF-8?Q?M=C3=B6llmann?= on Fri, 27 Dec 2024 07:04:54 +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:297812 Archived-At: > Cc: 75056@debbugs.gnu.org > From: Gerd Möllmann > Date: Fri, 27 Dec 2024 07:04:54 +0100 > > I can reproduce what you describe, I think, but I must admit that I'm a > bit at a loss at the moment. Something similar happens BTW if the server > is a GUI Emacs. Pretty weird. > > And then I found this in admin/notes/multi-tty, under known problems: > > * The single-kboard mode. > > 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. To unfreeze your session, switch to that > display and complete the recursive edit, for example by > pressing C-] ('abort-recursive-edit'). > > I am sorry to say that currently there is no way to break > out of this "single-kboard mode" from a frozen display. If > you are unable to switch to the display that locks the > others (for example because it is on a remote computer), > then you can use emacsclient to break out of all recursive > editing sessions: > > emacsclient -e '(top-level)' > > Note that this (perhaps) unintuitive behavior is by design. > Single-kboard mode is required because of an intrinsic Emacs > limitation that is very hard to eliminate. (This limitation > is related to the single-threaded nature of Emacs.) > > I plan to implement better user notification and support for > breaking out of single-kboard mode from locked displays. > > Also see the long list of things to do in the same file, which makes me > a bit wary. 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? 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.