From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Clemente Newsgroups: gmane.emacs.bugs Subject: bug#71343: 30.0.50; TTY frame doesn't automatically redisplay itself after having closed another frame Date: Thu, 6 Jun 2024 13:24:59 +0000 Message-ID: References: <86o78egucl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9183"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Paul Eggert , 71343@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 06 15:27:02 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 1sFD8v-0002Ea-7C for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 Jun 2024 15:27:01 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sFD8k-0001Lc-F2; Thu, 06 Jun 2024 09:26:51 -0400 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 1sFD8h-0001IW-Jm for bug-gnu-emacs@gnu.org; Thu, 06 Jun 2024 09:26:47 -0400 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 1sFD8h-0003aR-BH for bug-gnu-emacs@gnu.org; Thu, 06 Jun 2024 09:26:47 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sFD8v-0006pn-SX for bug-gnu-emacs@gnu.org; Thu, 06 Jun 2024 09:27:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Daniel Clemente Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 Jun 2024 13:27:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71343 X-GNU-PR-Package: emacs Original-Received: via spool by 71343-submit@debbugs.gnu.org id=B71343.171768041026254 (code B ref 71343); Thu, 06 Jun 2024 13:27:01 +0000 Original-Received: (at 71343) by debbugs.gnu.org; 6 Jun 2024 13:26:50 +0000 Original-Received: from localhost ([127.0.0.1]:52708 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sFD8k-0006pO-61 for submit@debbugs.gnu.org; Thu, 06 Jun 2024 09:26:50 -0400 Original-Received: from mail-ua1-f49.google.com ([209.85.222.49]:43327) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sFD8h-0006pB-Ml for 71343@debbugs.gnu.org; Thu, 06 Jun 2024 09:26:48 -0400 Original-Received: by mail-ua1-f49.google.com with SMTP id a1e0cc1a2514c-80ae09dce70so925561241.1 for <71343@debbugs.gnu.org>; Thu, 06 Jun 2024 06:26:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717680327; x=1718285127; darn=debbugs.gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=VPp3l48jD4pFUpMV6LIZ4RKyKCmVwTM+5c7uZkBe4nI=; b=RbK1IFyuZ+mBvTA+bR1v8THrwCir7jeuuqqGy4P6TrHpoenCoiI8YuoDenbKCmoCvv +6PwWEFw4nicSrBNES4ISF7tIAji01WB9zRc/P96O/ZVz5nAcpn0TsjQrs/pkSHxpMQk eSeSyetiwCJjh6ncz544qpOlQhNCltNC0SPGm/NcA90jWBwvEveWdVm5k0UprxNB+ySx 4BWSt0NpnCdrV1HA6fs/lcMYJBk6mD50L4HiZnoeDy1SS4Ymo97IOsmsc+ngkJ69pURm MqLo/dVX1bGyVGNNi9fkqwBvPXQPQOTlgA3qhO7FgZMOqZ8y95MnsnOzQGsboBSnmE4t ttgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717680327; x=1718285127; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=VPp3l48jD4pFUpMV6LIZ4RKyKCmVwTM+5c7uZkBe4nI=; b=Nk/riEzr0JW+I+4lA5PjM1B2mK1IV237Qs6thrzJdl38155tL1/UXIjvW8msumgJLp RzXMhTcvn0cPgcqp9umLexgItsS5WfJBwdHFM+6TqBGv9VoC8S4N5c+L4F4spPRVgXZr 5d9A2q6kkOJI50jsyupoRCCttH9iNo9rqW4XjW04c+FKdCDOfSQ4wFsXyViRZXNhWLgK c7ohmZ9wOdfzJBztKzVd7JN++fFXhKwLSWHsTFHiSub37m6yXSL4XyPxRbGwBcHimwUR 8gb3fFE0ZjVf/WUFyx611oZq+mga+yrXleUgrHw4xvV5RR/6BnhGS2VNkZrcQYBej9ip 1auQ== X-Forwarded-Encrypted: i=1; AJvYcCWh64ZzUXycHw7q8bmSmAmFbcfmIPcC/h2OKHozowYjRJFouhgQFCpKzYwp+e3CoCEcDkAzjHpu5OOrjCU/OnwFCZtjuY4= X-Gm-Message-State: AOJu0Yw24BkT6YOrhDS9ZGrWYazto0eb+eeGbUrjgKc6cWccgAsGU8b7 fdYevVokuwsv4B+kROfHMYPHc5ySjeM4/g1WzD7jAfdv3lUSMR+Gwa6C7nW3zZzECCio1wPEtOQ W+KP9YHuRFDBL+IQz9AmcHHGk1zc= X-Google-Smtp-Source: AGHT+IFRW1k2FpOUeGhPjq794KRMslGKQPAdCi0Lowm+TAiCUPu6TFNtzRQa33WKS6+KyUOtQVxxWVaOpJ7Innx+rTI= X-Received: by 2002:a05:6122:4584:b0:4eb:112e:6b74 with SMTP id 71dfb90a1353d-4eb48603e7bmr2874190e0c.8.1717680327476; Thu, 06 Jun 2024 06:25:27 -0700 (PDT) In-Reply-To: <86o78egucl.fsf@gnu.org> 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:286697 Archived-At: Note that I just posted a simpler way to understand this bug. No need to read the complex recipe with left/right columns. > I'm not sure this is a bug. Emacs switches to reading input from a > different terminal/keyboard when there's actually some input from that > terminal's keyboard. In the situation you described, the terminal > whose keyboard was active was killed. I'm guessing we get SIGHUP in > this case, so we could do something about it, but what exactly should > we do? Since no other keyboard provided any input, to which keyboard > to switch, and why? Random ideas, without knowing much about terminals. - Can't an X terminal detect =E2=80=9EI've been given X focus=E2=80=9C and = pass this signal to the program running inside it? - What if, when closing a TTY frame in emacsclient, all other frames are redisplayed - What if, when resizing the frame (something which Emacs detects), Emacs knows/detects that a frame was closed, and decides not to delay the redisplay? It's ok if it can't be fixed. I'm surprised that others didn't have this issue; but maybe not many are running TTY emacs (no X) inside an X window. I'm concerned about preventing cases in which the lack of redisplay can cause larger problems like mangled text. I just posted a comment at 71289 about a redisplay bug I saw, but I don't know whether it's related to closing or to resizing frames. Hopefully this issue (71343) can't cause mangled text in any situation.