unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: `pop-up-frames' and binding/setting user options [was: Documenting buffer display]
Date: Tue, 23 Oct 2018 15:57:35 -0700 (PDT)	[thread overview]
Message-ID: <2320bb1e-dfcd-4c90-a334-2a7f70d91483@default> (raw)
In-Reply-To: <jwvh8hcmsv8.fsf-monnier+emacs@gnu.org>

> > That's similar to using `special-display-buffer-names'.
> > (Not the same, but similar.)
> 
> You're confused: it's exactly the same.  `display-buffer-alist` is
> nothing but a replacement for `special-display-buffer-names`.

I should have said "I'm not sure it's always exactly
the same, but it's at least quite similar."

> You can do exactly the same with either of them.
> We had to introduce `display-buffer-alist` to replace
> `special-display-buffer-names` only for "minor" consistency reasons, to
> better interact with other ways to specify how to display a buffer.

Very good.



  parent reply	other threads:[~2018-10-23 22:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21 16:10 `pop-up-frames' and binding/setting user options [was: Documenting buffer display] Drew Adams
2018-10-21 17:01 ` Eli Zaretskii
2018-10-22  9:06 ` martin rudalics
2018-10-22 14:16   ` Drew Adams
2018-10-22 19:15     ` martin rudalics
2018-10-22 20:42       ` Drew Adams
2018-10-23  8:58         ` martin rudalics
2018-10-23 14:13           ` Drew Adams
2018-10-23 17:35             ` Stefan Monnier
2018-10-23 18:01               ` Drew Adams
2018-10-23 18:20                 ` Stefan Monnier
2018-10-23 18:28                   ` Stefan Monnier
2018-10-23 23:05                     ` Drew Adams
2018-10-23 22:57                   ` Drew Adams [this message]
2018-10-23 18:19             ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2320bb1e-dfcd-4c90-a334-2a7f70d91483@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).