all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: T.V Raman <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 16:46:28 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488978EADBE3C646D7E4C7AF3A39@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <p91fsb754rx.fsf@google.com>

> 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.

There's no reason to let the "perfect", Rube
Goldberg, hyper-complicated, `display-buffer-*"
apparatus be the enemy of the good-old, simple,
`pop-up-windows' behavior.

I need `pop-up-windows'.  But then, I've given
up on Emacs 28+ (even 27+) for my own use,
because of other unfortunate breakage.

Emacs 28 added this to the doc string of
`pop-up-windows':

 This variable is provided mainly for backward
 compatibility and should not be used in new code.

Used in code?  It's a _user option_.

Maybe what was meant was that new vanilla
Emacs code will no longer bother to respect
it.  (But if so, why put a guideline for Emacs
development in a user-option doc string?)

  reply	other threads:[~2023-02-15 16:46 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 ` Drew Adams [this message]
2023-02-15 17:20   ` [External] : " 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
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=SJ0PR10MB5488978EADBE3C646D7E4C7AF3A39@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=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.