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#68235: 29.1.90; Switching tabs stops following process output in selected window Date: Fri, 12 Apr 2024 09:30:37 +0300 Organization: LINKOV.NET Message-ID: <8634rrnmre.fsf@mail.linkov.net> References: <4bc98faf-5ebe-4c22-8c9f-04755785fde5@gmx.at> <86wmrjl8m3.fsf@mail.linkov.net> <39fe71c5-db40-49d1-b22b-37b52ed13865@gmx.at> <86jzn6yzae.fsf@mail.linkov.net> <021bb8c2-3f2d-4746-8f04-49f43cf57d16@gmx.at> <86il2mxmxd.fsf@mail.linkov.net> <3fe7e4b4-bc9a-4303-a87f-a360765c597f@gmx.at> <86le6wpok4.fsf@mail.linkov.net> <86msrbutsu.fsf@mail.linkov.net> <1305821a-6a0e-4cbc-82fb-bac229599c1b@gmx.at> <86sf0y2fg8.fsf@mail.linkov.net> <86il0rgh5a.fsf@mail.linkov.net> <86o7aiiiy8.fsf@mail.linkov.net> <86a5m1jg0g.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="9881"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: 68235@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Apr 12 08:50:19 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 1rvAjq-0002Oc-Dr for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 12 Apr 2024 08:50:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rvAjV-0008MP-Be; Fri, 12 Apr 2024 02:49:57 -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 1rvAjR-0008Jw-S8 for bug-gnu-emacs@gnu.org; Fri, 12 Apr 2024 02:49:53 -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 1rvAjR-0008QL-Jo for bug-gnu-emacs@gnu.org; Fri, 12 Apr 2024 02:49:53 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rvAja-0006yd-IY for bug-gnu-emacs@gnu.org; Fri, 12 Apr 2024 02:50: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: Fri, 12 Apr 2024 06:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 68235 X-GNU-PR-Package: emacs Original-Received: via spool by 68235-submit@debbugs.gnu.org id=B68235.171290457926553 (code B ref 68235); Fri, 12 Apr 2024 06:50:02 +0000 Original-Received: (at 68235) by debbugs.gnu.org; 12 Apr 2024 06:49:39 +0000 Original-Received: from localhost ([127.0.0.1]:57738 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rvAjB-0006th-2T for submit@debbugs.gnu.org; Fri, 12 Apr 2024 02:49:38 -0400 Original-Received: from relay3-d.mail.gandi.net ([2001:4b98:dc4:8::223]:59977) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rvAj7-0006rO-Bz for 68235@debbugs.gnu.org; Fri, 12 Apr 2024 02:49:35 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id D4E6060008; Fri, 12 Apr 2024 06:49:15 +0000 (UTC) In-Reply-To: (martin rudalics's message of "Thu, 11 Apr 2024 11:16:54 +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:283115 Archived-At: >> What is worse is that 'find-alternate-file' also resets >> 'buffer-file-name' to nil before killing the " **lose**" buffer. >> So even can't use a file name. > > Would replacing > > (kill-buffer obuf)))))) > > with > > (setq buffer-file-name ofile) > (setq buffer-file-number onum) > (setq buffer-file-truename otrue) > (kill-buffer obuf)))))) > > fix that? > > I never used 'find-alternate-file' and, after looking at its code for > the first time now, wouldn't touch it with a ten foot pole. Indeed, I have the same impression. > Using it in > 'image-next-file' seems a very bad idea: Is there any guarantee that the > assumptions about which buffer is current hold when running things like > 'kill-buffer-query-functions' or 'kill-buffer-hook' manually? Using 'find-alternate-file' in 'image-next-file' looks fine. There are no other problems. And revealing " **lose**" while restoring windows is not a bug deal.