JM> I think I've stumbled across another bug.... I can't get JM> display-buffer to display a buffer that is in a lower window. more acurately, I think the problem is that display-buffer was only displaying the currently selected buffer, which was my upper buffer. I have a proposed fix, but would like some folks check it out. It does seem to mess up my vm & bbdb interaction, but vm & gnus by themselves seem to work ok. I think the problem boils down to a missing "switch-to-buffer" in the code. As far as I can tell, it was determining the correct frame & buffer, it just never switched to it. but before submitting this to the patches review folks, I'd like more folks than just me testing it out. If I remember correctly, there have been reports in the past of buffers showing up in the wrong places. I've seen it at work myself. Very well could be related. --- window-xemacs.el.orig Mon Jun 22 00:15:15 1998 +++ window-xemacs.el Mon Jun 22 00:20:31 1998 ＠＠ -455,7 +455,9 ＠＠ (if (and window (or (not not-this-window-p) (not (eq window (selected-window))))) - (throw 'done (display-buffer-1 window))) + (progn + (switch-to-buffer buffer) + (throw 'done (display-buffer-1 window)))) ;; Certain buffer names get special handling. (if special-display-function