From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "raman@google.com" <raman@google.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Pop-up-windows vs display-buffer-take-action
Date: Wed, 15 Feb 2023 17:38:34 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F0EC7253752522666E19F3A39@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <831qmqc0be.fsf@gnu.org>
> > > I notice that pop-up-windows is now deprecated and the doc says to use
> > > the more complex display-buffer-take-action; however that newer option
> > > appears much more complex to configure; a recipe for getting
> > > something close to the old pop-up-windows t would be nice.
> >
> > +1000.
> >
> > `pop-up-windows' shouldn't have been deprecated.
>
> Are we now going to pick up fights lost 12 years ago? Really?
Not picking any fights. Expressing my sadness
that this happened. (But you lifted my spirits
by suggesting/hinting (?), below, that it's
_not_ deprecated.)
> And where do you see that this variable is deprecated, btw?
You're right that I didn't see the word
"deprecated" as such. If you think
"deprecated" is not meant, so much the better.
Glad to hear that.
To be clearer, the (28.2) doc string says this:
This variable is provided mainly for backward
compatibility and should not be used in new code.
To make 'display-buffer' behave as if this were t,
customize 'display-buffer-base-action' instead.
What I pointed out wrt referring to "used in new
code" stands. This seems to be telling someone
(users of the option in new code? who is that?
what kinds of code use options?) that they
should customize a different option.
If this wants to tell users to use one option
instead of another, why is it talking about using
the other (apparently nondeprecated) option "in
code"?
next prev parent reply other threads:[~2023-02-15 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 15:26 Pop-up-windows vs display-buffer-take-action T.V Raman
2023-02-15 16:46 ` [External] : " Drew Adams
2023-02-15 17:20 ` Eli Zaretskii
2023-02-15 17:38 ` Drew Adams [this message]
2023-02-15 18:07 ` Eli Zaretskii
2023-02-15 20:00 ` Drew Adams
2023-02-15 20:10 ` Eli Zaretskii
2023-02-15 20:49 ` T.V Raman
2023-02-16 7:37 ` Eli Zaretskii
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=SJ0PR10MB5488F0EC7253752522666E19F3A39@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
/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).