# HG changeset patch
# User Juri Linkov <juri@jurta.org>
# Date 1194819826 0
# Node ID d3745283de5f62a3d81993bdb6fccd2a6971d613
# Parent  430cc8630a39d855ae12a9eb28d166e0fb31c585
Add comments about isearch support.

diff -r 430cc8630a39 -r d3745283de5f lisp/doc-view.el
--- a/lisp/doc-view.el	Sun Nov 11 14:55:56 2007 +0000
+++ b/lisp/doc-view.el	Sun Nov 11 22:23:46 2007 +0000
@@ -97,9 +97,8 @@
 ;;
 ;; and modify them to your needs.
 
-;;; Code:
+;;; Todo:
 
-;; Todo:
 ;; - better menu.
 ;; - don't use `find-file'.
 ;; - Bind slicing to a drag event.
@@ -107,6 +106,31 @@
 ;; - get rid of the silly arrow in the fringe.
 ;; - improve anti-aliasing (pdf-utils gets it better).
 
+;;;; About isearch support
+
+;; I tried implementing isearch by setting
+;; `isearch-search-fun-function' buffer-locally, but that didn't
+;; work too good.  The function doing the real search was called
+;; endlessly somehow.  But even if we'd get that working no real
+;; isearch feeling comes up due to the missing match highlighting.
+;; Currently I display all lines containing a match in a tooltip and
+;; each C-s or C-r jumps directly to the next/previous page with a
+;; match.  With isearch we could only display the current match.  So
+;; we had to decide if another C-s jumps to the next page with a
+;; match (thus only the first match in a page will be displayed in a
+;; tooltip) or to the next match, which would do nothing visible
+;; (except the tooltip) if the next match is on the same page.
+
+;; And it's much slower than the current search facility, because
+;; isearch really searches for each step forward or backward wheras
+;; the current approach searches once and then it knows to which
+;; pages to jump.
+
+;; Anyway, if someone with better isearch knowledge wants to give it a try,
+;; feel free to do it.  --Tassilo
+
+;;; Code:
+
 (require 'dired)
 (require 'image-mode)
 (require 'jka-compr)