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#68081: 30.0.50; derived-mode and display-buffer-alist Date: Wed, 03 Jan 2024 13:59:20 +0200 Message-ID: <83frzezkyv.fsf@gnu.org> 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> <27b95070-c8d6-4607-bd21-bacabe13c673@gmx.at> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16412"; mail-complaints-to="usenet@ciao.gmane.io" Cc: germanp82@hotmail.com, 68081@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 03 13:00:25 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 1rKzv4-00040d-5Q for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 03 Jan 2024 13:00:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rKzuj-0005fJ-7G; Wed, 03 Jan 2024 07:00:01 -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 1rKzuh-0005f5-UT for bug-gnu-emacs@gnu.org; Wed, 03 Jan 2024 07:00: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 1rKzuh-0005Mo-MO for bug-gnu-emacs@gnu.org; Wed, 03 Jan 2024 06:59:59 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rKzuk-00033U-Cb for bug-gnu-emacs@gnu.org; Wed, 03 Jan 2024 07:00: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: Wed, 03 Jan 2024 12:00: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.170428319311699 (code B ref 68081); Wed, 03 Jan 2024 12:00:02 +0000 Original-Received: (at 68081) by debbugs.gnu.org; 3 Jan 2024 11:59:53 +0000 Original-Received: from localhost ([127.0.0.1]:51942 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rKzua-00032d-IY for submit@debbugs.gnu.org; Wed, 03 Jan 2024 06:59:52 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36456) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rKzuV-00032K-Uk for 68081@debbugs.gnu.org; Wed, 03 Jan 2024 06:59:51 -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 1rKzuN-0004pn-9X; Wed, 03 Jan 2024 06:59:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=5vqlRkCFUXR+YsAczVJ798KqSCblXhSRP2JmC6i4/wk=; b=qwPu7uafvHvR ZRoruAVnF0hf1unvnRT7L8Sc9K0hDJT8YGWOLb+aXBWJ8teRa1pPJ4vds8Ow8z3fgtVu19lg2D4Am TYh0MQ2d173vWI85qya7Vvs+E67HDh4++DQrIkQwxUUFBLxyBn8/nb+KOb3/2IyX4WDwCMlxbotQG xfopEIESJMkP2IVEA171uKJTLjL8h5LXH5RjbCZjhg+5SG2+3bCFEP+yxc74kqtNakDrcqBzpu1N1 74OjasFREqz90diMBH59pdG1CTkgsuPyQeb4sLIu8Yi16/8ilcPaWp67QlKS13CqzxZCwcVOTOsmV yfJ6fJpVdsH7YMomthrebQ==; In-Reply-To: <27b95070-c8d6-4607-bd21-bacabe13c673@gmx.at> (message from martin rudalics on Tue, 2 Jan 2024 11:46:26 +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:277271 Archived-At: > Date: Tue, 2 Jan 2024 11:46:26 +0100 > Cc: germanp82@hotmail.com, 68081@debbugs.gnu.org > From: martin rudalics > > > 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. Do other places that are affected by the same change do the same mistake of unconditionally calling pop-to-buffer?