From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#59862: quit-restore per window buffer Date: Wed, 10 Jul 2024 09:50:32 +0300 Organization: LINKOV.NET Message-ID: <86y169kafb.fsf@mail.linkov.net> References: <86fsds8mlm.fsf@mail.linkov.net> <86ttibq1w1.fsf@mail.linkov.net> <8243325e-ed03-4e9e-b64f-c8225fb6dc60@gmx.at> <18173da7-32e1-4f14-bbea-9a8fa66af7dd@gmx.at> <86plsxmc6d.fsf@mail.linkov.net> <86r0d4ezdc.fsf@mail.linkov.net> <0d01a044-d7d6-456a-9ba9-d987faad4332@gmx.at> <86frthjq4y.fsf@mail.linkov.net> <743dc4dd-cf09-4c5e-9209-b63a47480e0b@gmx.at> <86msnne7ut.fsf@mail.linkov.net> <86plsgrfvu.fsf@mail.linkov.net> <86le2b12ni.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40601"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/31.0.50 (x86_64-pc-linux-gnu) Cc: 59862@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jul 10 08:55:27 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 1sRREd-000ARW-RC for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 10 Jul 2024 08:55:27 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sRREC-0002w5-W7; Wed, 10 Jul 2024 02:55:01 -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 1sRRE9-0002vr-Su for bug-gnu-emacs@gnu.org; Wed, 10 Jul 2024 02:54:57 -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 1sRRE9-0005Hn-Eh for bug-gnu-emacs@gnu.org; Wed, 10 Jul 2024 02:54:57 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sRREE-0008Uh-BN for bug-gnu-emacs@gnu.org; Wed, 10 Jul 2024 02:55:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 10 Jul 2024 06:55:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59862 X-GNU-PR-Package: emacs Original-Received: via spool by 59862-submit@debbugs.gnu.org id=B59862.172059445032575 (code B ref 59862); Wed, 10 Jul 2024 06:55:02 +0000 Original-Received: (at 59862) by debbugs.gnu.org; 10 Jul 2024 06:54:10 +0000 Original-Received: from localhost ([127.0.0.1]:54721 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sRRDN-0008TL-Ix for submit@debbugs.gnu.org; Wed, 10 Jul 2024 02:54:09 -0400 Original-Received: from relay5-d.mail.gandi.net ([217.70.183.197]:51433) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sRRDL-0008Sp-Jl for 59862@debbugs.gnu.org; Wed, 10 Jul 2024 02:54:08 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 1D5371C0004; Wed, 10 Jul 2024 06:53:31 +0000 (UTC) In-Reply-To: (martin rudalics's message of "Tue, 9 Jul 2024 10:52:03 +0200") X-GND-Sasl: juri@linkov.net 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:288663 Archived-At: >> I suppose it will affect only interactive uses of 'kill-buffer'. > > Why? It affects all uses of 'kill-buffer'. I'm not sure about this, I just had a feeling that killing a temporary buffer should not affect its window. But a test case is needed to see if this is a real problem. >> PS: I noticed one difference between handling of frames and tabs: >> >> C-x 5 5 ;; other-frame-prefix >> C-h i ;; info >> C-h e ;; view-echo-area-messages >> q ;; quit-window >> This deletes the Info window, and doesn't delete the frame. >> Everything is correct. >> >> C-x t t ;; other-tab-prefix >> C-h i ;; info >> C-h e ;; view-echo-area-messages >> q ;; quit-window >> This doesn't close the tab (correct), >> but doesn't delete the Info window. >> This differs from the frame case that keeps >> only the Messages window on the frame. > > Suppose you do > > C-h i ;; info > C-h e ;; view-echo-area-messages > q ;; quit-window > > Then the difference is obvious. The C-h i reuses the one existing > window showing *scratch*. 'display-buffer-record-window' cannot tell > this case apart from the one where a user does want to show *scratch* > again in that window after being done with *info*. But there is no *scratch* in the list of previous buffers for 'C-x t t C-h i' (that can be confirmed when tab-line is enabled), so the user won't expect to show *scratch*. And indeed the frame case doesn't show *scratch*. I hoped that it would be possible for the tab case to do the same, but I don't know how the frame case is handled to do the right thing.