RE: error "Cannot switch buffers in (minibuffer | a dedicated) window"

["Drew Adams" <drew.adams@oracle.com>]

>     Wouldn't it make sense to just switch to the buffer in another window,
>     instead of raising an error?
>
> If you are trying to switch buffers in the minibuffer you probably
> don't know you're in the minibuffer. If you get an error you will
> probably type C-g which will get you out of it.  Switching buffers in
> another window and remaining in the minibuffer seems like a bad idea.

Thanks for the explanation. I guess that makes sense.

I agree that in this situation you probably don't know you're in the
minibuffer.

I was thinking that it would therefore be reasonable to exit the minibuffer
automatically at that point (the current level, if recursive) - that's
another way to remedy the mismatch between where the user thinks s?he is and
where s?he is. That is, instead of leaving the user in the minibuffer and
making him hit C-g to exit and then hit `C-x b' again, just assume that was
his intention.

Just assume, that is, that the user wants to (1) switch to the buffer and
(2) exit the minibuffer. This assumes that the main intention is to switch
to the buffer, with the particular window for the buffer not having a great
importance.

This would be a bit more DWIM and a bit less hands-off. The current approach
has the advantage of just informing the user of the state of things, without
assuming anything or trying to remedy the situation.

(Again, however, if we did this, it might be good to reserve it for
interactive buffer switching.)