bug#37840: Missing in the Emacs manuals:

[Konrad Podczeck]

> Am 08.11.2019 um 10:20 schrieb martin rudalics <rudalics@gmx.at>:
> 
> >> This means that for Konrad's scenario to work, the minimum requirement
> >> is
> >>
> >> (custom-set-variables
> >>   '(display-buffer-base-action
> >>     '((display-buffer-reuse-window display-buffer-pop-up-frame)
> >>       (reusable-frames . 0)))
> >>   '(display-buffer-alist
> >>     '(("\\*.*\\*" . (nil (inhibit-same-window . t)))))
> >>   '(switch-to-buffer-obey-display-actions t))

While this works in most cases, for me it still gives a problem with Speedbar: 
Suppose frame A has input focus, showing buffer A. Open Speedbar via the menu. 
Then the Speedbar frame pops up, with input focus, but with the same layout as 
frame A had, and a frame B opens, with the layput intended for the Speedbar 
frame, but showing buffer A. 

Konrad

> >
> > This doesn't look good, indeed.
> >
> > Then maybe switch-to-buffer-obey-display-actions should be replaced
> > by another variable switch-to-buffer-display-function that could be
> > customized to possible options #'pop-to-buffer-same-window,
> > #'pop-to-buffer or any other custom function (and nil by default).
> 
> We can do whatever we think best as long as Emacs 27 is not out yet.
> 
> If we leave things as they are we should probably mention explicitly
> that 'display-buffer-base-action' gets overridden when this option is
> set.  We should also say how 'switch-to-buffer-preserve-window-point'
> is or is not respected in that case (I'm slightly confused about how
> it works now).
> 
> Otherwise, I see no need for renaming the option.  We could simply
> allow its value to be an ordinary display action with functions and an
> alist and have 'switch-to-buffer' act accordingly.  Or am I missing
> something?
> 
> martin