From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: [External] : Pop-up-windows vs display-buffer-take-action
Date: Wed, 15 Feb 2023 22:10:41 +0200 [thread overview]
Message-ID: <835yc2advi.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54882612D8BC733E0FD7B14BF3A39@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Wed, 15 Feb 2023 20:00:35 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "raman@google.com" <raman@google.com>,
> "emacs-devel@gnu.org"
> <emacs-devel@gnu.org>
> Date: Wed, 15 Feb 2023 20:00:35 +0000
>
> So then what was the "fight" "lost 12 years
> ago"?
That sentence being inserted into the manual.
> It can't have been about that addition (in
> Emacs 28) to the doc string. Emacs 28 was
> released only a year ago.
This text in the manual is from 2011.
> But just what's being recommended to users
> about this option?
What the text says: don't use it in Lisp programs. And please don't
expect me to explain more, because I don't know about display-buffer
actions more than the next guy. I never use them, and try very hard
to stay as far as possible from them, to keep my sanity.
> 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.
>
> Indeed. How to get that behavior, or even
> close to it, with `display-buffer-base-action'?
> That's never been answered, to my knowledge.
My answer: keep using pop-up-windows.
next prev parent reply other threads:[~2023-02-15 20:10 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
2023-02-15 18:07 ` Eli Zaretskii
2023-02-15 20:00 ` Drew Adams
2023-02-15 20:10 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835yc2advi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--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 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.