Subject: bug#67249: 30.0.50; `same-frame` equivalent for `display-buffer-alist`

From: Stefan Monnier <[email-masked]>
Date: Sat, 09 Dec 2023 17:52:05 -0500

Hi Drew,

I have no idea what you're talking about.  Please double check
that you actually understand what the patch is doing (and take the
`Subject:` of this bug report as a good hint for the intended use),
and then clarify your argument.

For example, `pop-up-frames` is not deprecated.

        Stefan

Drew Adams [2023-12-09 22:40:00] wrote:

> +** New 'pop-up-frames' action alist entry for 'display-buffer'.
> +This has the same effect as the variable of the same name and takes
>                                  ^^^^^^^^
> +precedence over the variable when present.
>
> Please don't do that.  This is a user option,
> _not_ just a variable.  (And yes, it should
> continue to be supported, forever, regardless
> of the fact that it's been "deprecated".)
>
> `display-buffer' shouldn't override the user's
> choice for the behavior.
>
> From my point of view it's OK for a given
> command to override a user option, but only
> if the command's doc tells users that it does
> that.
>
> And a command can do that just by binding the
> option to nil.  Please don't let a parameter
> to `display-buffer' override this handy, simple
> user option.