From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: `pop-up-frames' and binding/setting user options [was: Documenting buffer display]
Date: Sun, 21 Oct 2018 20:01:57 +0300 [thread overview]
Message-ID: <83k1mbtere.fsf@gnu.org> (raw)
In-Reply-To: <d7d4a283-1014-40bc-89a9-53843b589549@default> (message from Drew Adams on Sun, 21 Oct 2018 09:10:20 -0700 (PDT))
> Date: Sun, 21 Oct 2018 09:10:20 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> > A user option has to be respected.
>
> A _user_ has to be respected.
Yes. And they _are_ respected.
I don't really understand what are you arguing about here. There's
nothing wrong in deprecating certain interfaces if we find that they
get in the way of Emacs development and/or maintenance. As long as
the "old ways" are supported and documented, no one and nothing is
harmed. You've voiced your opinion in favor of pop-up-frames etc.,
and against favoring display-buffer and friends, and we happen to
disagree with it. There's no need to continue arguing that same
argument, as the disagreement is clear. It is entirely okay for Emacs
developers to try to encourage users to use the interfaces we favor,
even if you happen to disagree.
next prev parent reply other threads:[~2018-10-21 17:01 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1mbtere.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--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.