Re: frames dedicated to buffers, or, always see specific buffers in a specific frame

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> Other from that I don't see anything hackish with your approach if the
>> idea is to make `switch-to-buffer' do what you want when it's called
>> from other code (which ideally should not happen).  In this case you
>> might also want to advice `switch-to-buffer-other-window' accordingly.

I don't see why that would be necessary: switch-to-buffer-other-window
calls display-buffer (well, pop-to-buffer) so it should honor
display-buffer-alist.

> Ideally I would want anywthing with the meaning "switch to some
> buffer" (be it `pop-to-buffer', `switch-to-buffer-other-window`,
> `display-buffer`, etc...) to be be hookable at some common point, much
> as is already done with `display- buffer'.

Other than switch-to-buffer they all go through display-buffer and obey
the display-buffer-* hooks.

switch-to-buffer is special because there are various circumstances
where it's more important for it to only affect the selected-window then
it is to display the specified buffer.

> Specifically, how can I prevent `display-buffer' from stopping at one of
> the actions that I specify in `display-buffer-alist'?

Don't return nil?

More specifically, your joaot/browse-buffer-in-special-frame should
return the window it used to display the buffer.


        Stefan