Re: switch-to-buffer: for interactive use only

[Juanma Barranquero]

On Fri, Jul 8, 2011 at 22:12, Chong Yidong <address@hidden> wrote:

> Why does `switch-to-buffer' need to only affect the selected window?
> What's wrong with using a different window, instead of signaling a
> error, if the selected window can't be used?

That would resurrect the bug recently fixed in bs-cycle-next where it
opened another window when the selected one was strongly dedicated. It
is called "cycle", not "bring-me": either it can cycle a new buffer
into the window, or it should say that it cannot. That's what it does
now, and that's the right thing to do.

For some operations on a buffer with a strongly dedicated window, it
makes sense to pop up another window; for some others, it does not.
Conflating both is never going to be a good answer. Well, strictly
speaking, we can do that and use `display-buffer-alist' to allow the
user to override it; but bs-cycle-next, and operations of that kind,
should do the right thing out of the box.

    Juanma