From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Documenting buffer display
Date: Wed, 24 Oct 2018 17:48:43 +0300 [thread overview]
Message-ID: <83h8hbs8ms.fsf@gnu.org> (raw)
In-Reply-To: <5BD03F18.1020100@gmx.at> (message from martin rudalics on Wed, 24 Oct 2018 11:44:56 +0200)
> Date: Wed, 24 Oct 2018 11:44:56 +0200
> From: martin rudalics <rudalics@gmx.at>
> 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.
next prev parent reply other threads:[~2018-10-24 14:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 12:20 Documenting buffer display martin rudalics
2018-10-20 13:21 ` Eli Zaretskii
2018-10-20 18:02 ` martin rudalics
2018-10-21 12:56 ` Eli Zaretskii
2018-10-22 9:06 ` martin rudalics
2018-10-22 13:55 ` Eli Zaretskii
2018-10-22 19:14 ` martin rudalics
2018-10-22 19:27 ` Eli Zaretskii
2018-10-23 8:58 ` martin rudalics
2018-10-23 11:26 ` Pierre-Yves Luyten
2018-10-23 13:45 ` martin rudalics
2018-10-23 17:40 ` Stefan Monnier
2018-10-23 14:04 ` Drew Adams
2018-10-23 18:18 ` martin rudalics
2018-10-23 15:18 ` Eli Zaretskii
2018-10-23 18:23 ` martin rudalics
2018-10-23 19:07 ` Eli Zaretskii
2018-10-24 9:44 ` martin rudalics
2018-10-24 14:48 ` Eli Zaretskii [this message]
2018-10-24 17:40 ` martin rudalics
2018-10-24 18:25 ` Eli Zaretskii
2018-10-25 20:42 ` Juri Linkov
2018-10-23 15:52 ` Alan Mackenzie
2018-10-23 18:25 ` martin rudalics
2018-11-08 19:25 ` martin rudalics
2018-10-22 1:39 ` Michael Welsh Duggan
2018-10-22 5:54 ` Eli Zaretskii
2018-10-20 15:22 ` Drew Adams
2018-10-20 18:02 ` martin rudalics
2018-10-20 18:24 ` Drew Adams
2018-10-21 8:22 ` martin rudalics
2018-11-04 9:06 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8hbs8ms.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.