From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#68081: 30.0.50; derived-mode and display-buffer-alist Date: Tue, 2 Jan 2024 11:46:26 +0100 Message-ID: <27b95070-c8d6-4607-bd21-bacabe13c673@gmx.at> References: <83r0j6774p.fsf@gnu.org> <342c493e-b0ba-40a8-8023-58a9bb04abd6@gmx.at> <83v88h5j7z.fsf@gnu.org> <9fc1e566-d99e-479a-bb38-fce6a964dfc0@gmx.at> <83edf43soc.fsf@gnu.org> <9cfb6641-9fda-4623-8623-a17341369c18@gmx.at> <8db30606-c98c-4078-a448-6ad31bd59768@gmx.at> <83plyl1c47.fsf@gnu.org> Reply-To: martin rudalics Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22857"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: germanp82@hotmail.com, 68081@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 02 11:47:10 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 1rKcIg-0005k1-3P for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 02 Jan 2024 11:47:10 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rKcIY-0000Lq-Cz; Tue, 02 Jan 2024 05:47:02 -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 1rKcIW-0000Lf-Ft for bug-gnu-emacs@gnu.org; Tue, 02 Jan 2024 05:47:00 -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 1rKcIW-0004cd-8I for bug-gnu-emacs@gnu.org; Tue, 02 Jan 2024 05:47:00 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rKcIY-0005qk-I7 for bug-gnu-emacs@gnu.org; Tue, 02 Jan 2024 05:47:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 02 Jan 2024 10:47:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 68081 X-GNU-PR-Package: emacs Original-Received: via spool by 68081-submit@debbugs.gnu.org id=B68081.170419240022440 (code B ref 68081); Tue, 02 Jan 2024 10:47:02 +0000 Original-Received: (at 68081) by debbugs.gnu.org; 2 Jan 2024 10:46:40 +0000 Original-Received: from localhost ([127.0.0.1]:49466 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rKcIC-0005ps-BS for submit@debbugs.gnu.org; Tue, 02 Jan 2024 05:46:40 -0500 Original-Received: from mout.gmx.net ([212.227.15.15]:35699) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rKcI9-0005lr-G8 for 68081@debbugs.gnu.org; Tue, 02 Jan 2024 05:46:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.at; s=s31663417; t=1704192387; x=1704797187; i=rudalics@gmx.at; bh=bnZAzzndsC5L0HKbLkgSs7i7W2hfdDGtbLvW8tWluvE=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From: In-Reply-To; b=nNUX0EuGMdhFmD6L+Jzn+fI/Nctiqh8xcEDxJ49i7w5sqXpYGiyM09/1gKq8ZOTs z+hzdH7/Hj2mrX2kYUmTmT3kqkWHgEOv7GynDAVHZQjabo92ZGH9YWKOgMkzu8E56 222VUHXqXGKICpqoEAnQfqvQjN3HLsVgSkKGvqtn4ZJXUujEQQh7WccsjV80XPGSw vMz9qeGJGMzH1CPJq1R9qXbn0VRzuMlPS+EGUacy7iPbpOxsMsK/lyIvC+KsFZqAY L59kHSwf1G7ZSQNKg2jXKhngULwBCksJGbQDdBe5jQO8d3CEBgPoiVIwlULEJ548T 3eYOd/fqQiGWYJqJEA== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Original-Received: from [192.168.31.113] ([213.142.96.121]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MAfUo-1rVZal00oC-00B6VA; Tue, 02 Jan 2024 11:46:27 +0100 Content-Language: en-US In-Reply-To: <83plyl1c47.fsf@gnu.org> X-Provags-ID: V03:K1:9g8Td8sRhayLP2YDQkhAsAdizqZXvrIzTJYUh8nwJ+wdm6Qkds2 R6jhA7vkE95hZrfN/vjte2osb4CfB3fo4hwmeSk+C2TcB8nyreriDQxsjvItqGrfGxRP47r aGcAOMq9bkbcSlV7YO9Ki6bmgzZOkFtrwAmBMAgGObNC1uAxA/KCEsAKiGWHjEsxhOqcFCI tDO3SeYbEli+51EsW5jog== UI-OutboundReport: notjunk:1;M01:P0:1bwiGj1rrAk=;9o+shEDLs9DL+rTHe3JgbJmCGYp diVGRFPMEA0ca94buOEcz7KWVBKyLBhK4+Qi5tgtr9OOOJzpdaVNHT8VUZ5WbwNG5Hdm9cMlo PtLvnssH/F6IjoQgMMNGmgHkChN1vIsgf3khcD14y71DqRHNgOlIVRotV17xVntbGaQQ0jv5V NTc6c5t225b5IO6EgcEP1Hkk1eEONhHGx88aFJezjeYEB1yY0nJ5uo6+qCcaooIsfw4Y5yPWd hXjohoWwz6n6nkJJNnzCXyNoybsuSUvvNZcIyjFtT101Loe828oRxA3OOhuGwAIXgHb1Ht4wq VnQCafsZXjasnCDnktQKz01F9ZwzDW9iKWIH0F6WdEl9NLxy79e1CTSQnrFCDkBrkdVE5bklm mvzPxu67qDlxCTcI3pNv+ZxrDBLOHlzpRCVLo8Uc3QjX36arDgzPD67fGROFJNgI0wZJSuBvh 00QE8/Q9sx65t8fdsvohh848o37QNm33Wk2Vv2TVHaNmcmlbUkiifNV2KUJpPCOugFIVFO5OK vpn0x+2GTRESuGtZ+cvzHmoPktEulOe/yIZHbCVln9h0WrzV/LB2ZNSxzNIWIpbKkgE1V7XkC bij8kP/jgo52cLulEukGYhJksbwNYgWNQL+IX5F/OY0sRtKAmOAdcqbSkzCFmZfjGUPYfauA9 eneFDy4sX64TdgiLwmcPWB3FplqNWE1WuHzeI6l9Ry5Etngi7p7hZd3CCrA+Dx5jNaJD0l3P9 7h9q4KFyNwrTFy3rHEx6OTWaAx/W4rUsUHkI6Imgbj8o4wusQRBcXLCCJBVAUW/17oRQ9x+m 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:277221 Archived-At: > Thanks, but now I wonder whether we should revert the change which > made display-buffer call buffer-match-p. The problem is not with 'display-buffer'. The problem is with 'pop-to-buffer' and 'switch-to-buffer'. What would you tell people who already customized 'display-buffer-alist' and are happy with how it works with 'display-buffer'? > It sounds like fixing the > breakage in any other way is either hard or fragile or nigh > impossible. 'info' initially used 'switch-to-buffer' (if (get-buffer "*info*") (switch-to-buffer "*info*") (Info-directory)))) Later it called 'pop-to-buffer' as (if (get-buffer "*info*") (pop-to-buffer "*info*") (Info-directory)))) The breakage occurred when it started to call (pop-to-buffer "*info*") without checking whether that buffer exists. It sometimes backfires to use a feature meant for interactive use (like 'pop-to-buffer' creating its buffer autonomously) in non-interactive calls. Sometimes it happens decades after that feature was misused. BTW note that C-h F ignores _any_ efforts you put into customizing 'display-buffer-alist' like say (customize-set-variable 'display-buffer-alist '(("\\*info\\*" display-buffer-pop-up-window (inhibit-same-window . t)))) So there is worse than C-h i. martin