From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Documenting buffer display Date: Wed, 24 Oct 2018 17:48:43 +0300 Message-ID: <83h8hbs8ms.fsf@gnu.org> References: <5BCB1D82.3020108@gmx.at> <834ldgvjmj.fsf@gnu.org> <5BCB6DAE.30209@gmx.at> <83mur7tq4f.fsf@gnu.org> <5BCD92FF.8070905@gmx.at> <838t2qt79v.fsf@gnu.org> <5BCE21AC.6030904@gmx.at> <831s8hu6i8.fsf@gnu.org> <5BCEE2B5.9090205@gmx.at> <83sh0wsnd6.fsf@gnu.org> <5BCF672A.4080605@gmx.at> <83k1m8scq9.fsf@gnu.org> <5BD03F18.1020100@gmx.at> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1540392918 17476 195.159.176.226 (24 Oct 2018 14:55:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 24 Oct 2018 14:55:18 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 24 16:55:14 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gFKYz-0004Q2-TF for ged-emacs-devel@m.gmane.org; Wed, 24 Oct 2018 16:55:14 +0200 Original-Received: from localhost ([::1]:48890 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFKb6-0002Yo-Cv for ged-emacs-devel@m.gmane.org; Wed, 24 Oct 2018 10:57:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFKXJ-0000E7-EM for emacs-devel@gnu.org; Wed, 24 Oct 2018 10:53:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFKSq-0000oA-Qo for emacs-devel@gnu.org; Wed, 24 Oct 2018 10:48:58 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:48209) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFKSm-0000n7-Ml; Wed, 24 Oct 2018 10:48:50 -0400 Original-Received: from [176.228.60.248] (port=4162 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gFKSl-0003KI-Co; Wed, 24 Oct 2018 10:48:48 -0400 In-reply-to: <5BD03F18.1020100@gmx.at> (message from martin rudalics on Wed, 24 Oct 2018 11:44:56 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:230629 Archived-At: > Date: Wed, 24 Oct 2018 11:44:56 +0200 > From: martin rudalics > CC: emacs-devel@gnu.org > > >> What do you suppose a user to do if 'pop-to-buffer-same-window' is the > >> _only_ alternative an application offers to display a buffer? > > > > They should ask for a separate command, or for a user option to have > > the buffer displayed not in the selected window. That option could > > (but doesn't have to) be implemented under the hood using action > > lists, of course. > > That user option already exists as 'display-buffer-alist'. That > option was invented precisely for that purpose. That option has no > other purpose. Just to clarify what I meant: I did NOT mean display-buffer-alist. I meant something like this: find-dired is an interactive compiled function... [...] By default, display the buffer in the selected window; NO-SELECT non-nil (interactively, prefix argument) means display the buffer in a window other than the selected one instead. or By default, display the buffer in the selected window, but if the value of `find-dired-no-select' is non-nil, display the buffer in a window other than the selected one instead. This is our usual method of letting users tweak some minor aspects of how a command works, and I see no reason why users would instead have to construct action lists to do the same for commands that happen to use display-buffer internally.