# HG changeset patch
# User Gerd Moellmann <gerd@gnu.org>
# Date 997447659 0
# Node ID cdd382cc0e92346ddbffab039a9ab3ee7412694d
# Parent  a83fdca83ae315599ed6a7aaf0ebc77e3fd0cd7c
(isearch-other-meta-char): Don't switch to the
buffer of a window clicked on, when the current buffer is
in Isearch mode.

diff -r a83fdca83ae3 -r cdd382cc0e92 lisp/isearch.el
--- a/lisp/isearch.el	Fri Aug 10 10:59:06 2001 +0000
+++ b/lisp/isearch.el	Fri Aug 10 12:47:39 2001 +0000
@@ -1243,10 +1243,25 @@
 	       (pop unread-command-events)
 	       (setq main-event (car unread-command-events)))
 
-	     ;; If we got a mouse click, maybe it was read with the buffer
+	     ;; If we got a mouse click event, that event contains the
+	     ;; window clicked on. maybe it was read with the buffer
 	     ;; it was clicked on.  If so, that buffer, not the current one,
 	     ;; is in isearch mode.  So end the search in that buffer.
-	     (if (and (listp main-event)
+
+	     ;; ??? I have no idea what this if checks for, but it's
+	     ;; obviously wrong for the case that a down-mouse event
+	     ;; on another window invokes this function.  The event
+	     ;; will contain the window clicked on and that window's
+	     ;; buffer is certainaly not always in Isearch mode.
+	     ;;
+	     ;; Leave the code in, but check for current buffer not
+	     ;; being in Isearch mode for now, until someone tells
+	     ;; what it's really supposed to do.
+	     ;;
+	     ;; --gerd 2001-08-10.
+
+	     (if (and (not isearch-mode)
+		      (listp main-event)
 		      (setq window (posn-window (event-start main-event)))
 		      (windowp window)
 		      (or (> (minibuffer-depth) 0)