When read-from-minibuffer is setting up things for the internal call,
it chooses " *Minibuf-n" as the buffer for recursive minibuffers, but
in the level 0 case it just grabs whatever buffer is currently
displaying in the minibuffer window.
This can't possibly be right, can it? It is partly responsible for the
failure of quail to work in the minibuffer.
Following patch fixes that. If correct, it should also be applied in
21.5.
--- /home/jcb/XEmacs-Dist-21.4.22/lisp/minibuf.el 2005-12-07 01:16:49.000000000 +0000
+++ XEmacs-21.4.22-mods/lisp/minibuf.el 2009-08-07 16:03:38.000000000 +0100
@@ -408,10 +408,8 @@
(owindow (selected-window))
(oframe (selected-frame))
(window (minibuffer-window))
- (buffer (if (eq (minibuffer-depth) 0)
- (window-buffer window)
- (get-buffer-create (format " *Minibuf-%d"
- (minibuffer-depth)))))
+ (buffer (get-buffer-create (format " *Minibuf-%d"
+ (minibuffer-depth))))
(frame (window-frame window))
(mconfig (if (eq frame (selected-frame))
nil (current-window-configuration frame)))
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta