Re: obsolete variable, use 2nd arg of `display-buffer' instead]

[martin rudalics <rudalics@gmx.at>]

> I do not and will not use the customization ui.
> I want my settings where I can read and modify them.

This is a pity for two reasons: If experienced developers never use the
UI all feedback in this area will come from inexperienced users.  That's
why the customization interface occasionally lags behind.  Moreover, I
spent some time writing the customization for this option and now do not
find anyone to go through it.

But what I rather meant was using the customization UI as a starter, get
a first version from there and then continue hacking the result.

> it produces a lot of separate entries like
>  (((name . "*acl-listener*"))
>   fun-with-args
>   (fun-with-args special-display-popup-frame #1#))
>  (((name . "*scheme*"))
>   fun-with-args
>   (fun-with-args special-display-popup-frame #1#))
>  (((name . "*allegro*"))
>   fun-with-args
>   (fun-with-args special-display-popup-frame #1#))
>  (((name . "*cmu*"))
>   fun-with-args
>   (fun-with-args special-display-popup-frame #1#))
>
> I think it would be better to group them together like I do above.

Agreed.  I hope I can do that - `special-display-regexps' is difficult
to parse.

> also, it converts same-window-buffer-names into
>  (((name . "*Diff*")) reuse-window (reuse-window same))
> how is this different from
>  (((regexp . ".*")) reuse-window (reuse-window nil same 0))

"(reuse-window same)" stands for "reuse the same (selected) window, no
matter which buffer it shows" (which is what `same-window-buffer-names'
stands for).

"(reuse-window nil same 0)" stands for "reuse any window showing the
same buffer on any visible or iconified frame".

So if you can reformulate my doc-string to make this clear, please do
so.

> also, special-display-popup-frame is marked as obsolete, so
> display-buffer-alist-set should not be producing it.

Hmmm...  So I'll have to revert the obsoletion declaration for this.  Or
interpret the functionality of `special-display-popup-frame' in terms of
`display-buffer-alist' which would be better but harder.  I'll tell you
as soon as I know what I can do.

> also, how is
>  (.... fun-with-args (fun-with-args special-display-popup-frame #1#))
> different from
>  (.... pop-up-frame (pop-up-frame-alist ....))

`special-display-popup-frame' is a special function that can, for
example, reuse a window for showing the buffer.  `pop-up-frame' means to
call either `pop-up-frame-function' or, if this is undefined
`make-frame', but in any case always pop up a new frame and never reuse
an existing window.

Thanks for going through this, martin