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 16:05:35 -0700 (PDT) [thread overview]
Message-ID: <e9ec6b01-b841-4811-99da-d129ce1d8063@default> (raw)
In-Reply-To: <jwv7ei8msd7.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`.
>
> Hmm... rereading the above, I believe my wording was very poorly chosen.
> I didn't mean it to sound so critical. Also this whole part of your
> message was in the end largely irrelevant to your actual message.
> So, please try and just ignore the above, sorry,
No problem. We're all trying to work something out
here, and maybe come to an approximate consensus.
Opinions can be strong sometimes even when the real
differences seem slight to others. And email is not
necessarily the easiest way to find common ground.
next prev parent reply other threads:[~2018-10-23 23:05 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 [this message]
2018-10-23 22:57 ` Drew Adams
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=e9ec6b01-b841-4811-99da-d129ce1d8063@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).