# HG changeset patch
# User Juanma Barranquero <lekktu@gmail.com>
# Date 1049547482 0
# Node ID fedb9513a26e94515fcda77144f8a2e9b86780c8
# Parent  33c5c2bf40c2dfec969d759ea3d7cb37a813f919
(emacs-lisp-mode): Add prefix/suffix matching regexps.

diff -r 33c5c2bf40c2 -r fedb9513a26e lisp/info-look.el
--- a/lisp/info-look.el	Sat Apr 05 03:11:36 2003 +0000
+++ b/lisp/info-look.el	Sat Apr 05 12:58:02 2003 +0000
@@ -756,9 +756,19 @@
 (info-lookup-maybe-add-help
  :mode 'emacs-lisp-mode
  :regexp "[^][()'\" \t\n]+"
- :doc-spec '(("(emacs)Command Index")
-	     ("(emacs)Variable Index")
-	     ("(elisp)Index")))
+ :doc-spec '(;; Commands with key sequences appear in nodes as `foo' and
+             ;; those without as `M-x foo'.
+             ("(emacs)Command Index"  nil "`\\(M-x[ \t\n]+\\)?" "'")
+             ;; Variables normally appear in nodes as just `foo'.
+             ("(emacs)Variable Index" nil "`" "'")
+             ;; Almost all functions, variables, etc appear in nodes as
+             ;; " - Function: foo" etc.  A small number of aliases and
+             ;; symbols appear only as `foo', and will miss out on exact
+             ;; positions.  Allowing `foo' would hit too many false matches
+             ;; for things that should go to Function: etc, and those latter
+             ;; are much more important.  Perhaps this could change if some
+             ;; sort of fallback match scheme existed.
+             ("(elisp)Index"          nil "^ - .*: " "\\( \\|$\\)")))
 
 (info-lookup-maybe-add-help
  :mode 'lisp-interaction-mode