From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#16767: [External] : bug#16767: 24.3.50; `C-x 5 b' for special-display buffers Date: Wed, 8 Sep 2021 10:27:54 +0200 Message-ID: <73026fca-0b01-6e3f-5ab4-1c25ff848a13@gmx.at> References: <530093D6.70002@gmx.at> <87sfyihx4q.fsf@gnus.org> <79c1e006-3871-ee08-dd3d-df7957f7343b@gmx.at> <2b306c6f-8c25-b8c2-0390-305e5c42036d@gmx.at> <8fe2ebb5-c2d6-fbb5-8651-fb2227affba7@gmx.at> 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="11166"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , "16767@debbugs.gnu.org" <16767@debbugs.gnu.org> To: Drew Adams , Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 08 10:29:57 2021 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 1mNsxw-0002hs-Ma for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 08 Sep 2021 10:29:56 +0200 Original-Received: from localhost ([::1]:36342 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mNsxv-0004xv-NX for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 08 Sep 2021 04:29:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47774) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mNsx4-00045W-OH for bug-gnu-emacs@gnu.org; Wed, 08 Sep 2021 04:29:06 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46987) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mNsx4-0006rG-G6 for bug-gnu-emacs@gnu.org; Wed, 08 Sep 2021 04:29:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mNsx4-00070t-2Z for bug-gnu-emacs@gnu.org; Wed, 08 Sep 2021 04:29:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 08 Sep 2021 08:29:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16767 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo notabug Original-Received: via spool by 16767-submit@debbugs.gnu.org id=B16767.163108969326882 (code B ref 16767); Wed, 08 Sep 2021 08:29:02 +0000 Original-Received: (at 16767) by debbugs.gnu.org; 8 Sep 2021 08:28:13 +0000 Original-Received: from localhost ([127.0.0.1]:58533 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mNswG-0006zV-P0 for submit@debbugs.gnu.org; Wed, 08 Sep 2021 04:28:13 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:33279) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mNswF-0006zF-BM for 16767@debbugs.gnu.org; Wed, 08 Sep 2021 04:28:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1631089678; bh=IZq71xC9NGNEsLYQ6wcTtvJeaG+F2xc6Ck59mabi7Ak=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=GtwM2b/D0l2sA+mD8XJd1KZbVeODsA4Mw3csFTlSBtqJLyUpuTEmS12OrjQEl++Vn mZF43vBM0eVMlkKTujRyFvs3B8nccSC+f1UtAGEAPVsBkcj67A+UNnI40q4wbGqiiY DYvG7SVOe2iao++u+GNJ4ZqSz2OaenHOpT/FnhYw= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.100] ([212.95.5.191]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1Mj8mb-1muAx63rSH-00fEwk; Wed, 08 Sep 2021 10:27:58 +0200 In-Reply-To: Content-Language: en-US X-Provags-ID: V03:K1:FrlUutWMbsXk1csV9VZfa30PQwJXO4/0f2PR+8QdEIFX+yTruwl 3UYf/di9JCvSDBVaI/Z9g6WHkhKr+6tuMB5r7MuJV9QiOFBQOuyDWz7BkRdymK5JwX50jlj c3feZ4MpYqlxP8Y5SRlXaO5zvffK6tUyzwQSPNm1afYlz2DBXFO3xiLia9PvkyeVLH3KqyG lsDTMMyE7gNFzKX5qQk8Q== X-UI-Out-Filterresults: notjunk:1;V03:K0:f+Qix4BUnuA=:Ins0NMYdq/LtxeTjpeNcjf MTkpWvMZf3v3tLIa4PMTQ2taB/H6qvnFbIwfZMuCkWOp48h1gwxMoCElzQwEfjTGjxeE/x+bc ppRIZ3wsvgsnuhj15rk8kDLh+dkVLHQ8muscK8g3bLHX+Pfzwm/ZmLYP+t5NYAJW4ePT/gkk5 kmadTaP/oE0JkenWsDoBxKm9Fbu+uD/84mbkyEOiKhPjktFMGGvQvphO3DlPIW4PyvF6v+lzs GolddgcVa/6eZj7TNR3rQeBpGEa2lZMFFSHqnc+AZTmB4i1N5lnXcMh9uybniws0lQRAYna3l D4yYx0BYhi6i+RpV03Ia8nbytyJinYr8B7EKjJ7hLOzE62B2OIGvSXRlDE85gIE/edpfY8SEl iWKyaCCSNPevUYowioLi/6FuYgX194aCZJZBoV+xQqnAfS6EHF3To3fKP03smejjLQE1TQ4EG U7TJxHZ6O23k/XRdGcnKfP8jZGpTM0L2Js8oXhrl5B3iqhaXKOTgxvkctaTqRINNEXLy51RNm hh/wpzkfzAM9COCMOExd0FSfuzPSTHzUDrskTfTB115iUEdb7UruiRyqQRJ8VtvQrnbENYMgt Lzh3JL2sBzfwW9IHexgZXKi84XRMHyCAB2PEvMEviKN1ZP9mIjgg75iBw4QsOBPjUyk/HoNBA r+CSSkctYlSbW/0FDjGRlzgjC/CDH1ze9Hq5SZ28FWs1d3wDVen+V+qHzf423c9DikG7mZl7v 5buCYVggaVkb7OnBjiH2ZYdudET/R6dejjU4LRH3WygEIlit/O9r1ayopmikYBTGvaHCQKbC 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" Xref: news.gmane.io gmane.emacs.bugs:213801 Archived-At: > You can say that the `special-display-*' options > override default behavior, and of course they do. > But nothing says that they override THAT behavior, > of using a separate frame. Nothing in the doc, > AFAICT. You've been customizing the option `special-display-regexps' which specifies a List of regexps saying which buffers should be displayed specially. in a way to display *scratch* specially. The doc-string of that option continues saying that Displaying a buffer with `display-buffer' or `pop-to-buffer', if any regexp in this list matches its name, displays it specially using `special-display-function'. `special-display-popup-frame' \(the default for `special-display-function') usually displays the buffer in a separate frame made with the parameters specified by `special-display-frame-alist'. and since you have not customized `special-display-function' and the doc-string of `special-display-popup-frame' tells to Pop up a frame displaying BUFFER and return its window. If BUFFER is already displayed in a visible or iconified frame, raise that frame. C-x 5 b which runs `switch-to-buffer-other-frame' whose doc-string says This uses the function `display-buffer' as a subroutine to display the buffer; see its documentation for additional customization information. uses the selected window which displays *scratch* already and makes sure that its frame is risen. > All they do is say that the given buffers use > frames with particular frame parameters. They > say nothing at all about the use of a same frame > or a different frame. And that means (should > mean) that the default behavior described for > the functions cited should remain the case, > except for the behavior (e.g. frame parameters) > prescribed by the `special-display-*' options. > Those options say nothing at all about using > another or the same frame. The doc-string of `special-display-popup-frame' says that. > They say nothing at > all about `C-x 5' behavior. The doc-string of `switch-to-buffer-other-frame' says that. > What's needed is a way to NOT have prefix key > `C-x 5' use the same window for some specified > set of buffers. Or (better) to have `C-x 5' > keys NOT use the same window for ANY buffers. The default behavior does that. You override it with your customizations. > The default behavior for special-display-* > is to reuse any window that already > displays the buffer, so in order to make > C-x 5 2 meaningful we'd clearly want to skip > this part of the usual special-display-* > behavior. So you were aware of the fact that C-x 5 2 behaves like that all the time and yet insisted that our code and/or docs are wrong? Do you ever think that going through your bug reports takes peoples' time? martin