> That seems unfortunate.  Can we somehow make Speedbar insulated from
 > the switch-to-buffer customizations?

The attached patch should do that.  But there are probably too many
similar cases out there.  Strictly spoken we should check each of our
'switch-to-buffer' calls for whether to

(1) convert it to 'set-window-buffer' (so no customization ever
     affects it),

(2) bind 'switch-to-buffer-obey-display-actions' to nil around it (to
     bow out comme il faut when the window is a minibuffer window or
     dedicated to its buffer),

(3) call 'pop-to-buffer-same-window' instead, or

(4) leave it alone.

martin