comparison lisp/info-look.el @ 50451:fedb9513a26e

(emacs-lisp-mode): Add prefix/suffix matching regexps.

50450:33c5c2bf40c2

	      "`" "\\({[^}]*}\\)?'")))

(info-lookup-maybe-add-help
 :mode 'emacs-lisp-mode
 :regexp "[^][()'\" \t\n]+"
 :doc-spec '(("(emacs)Command Index")
	     ("(emacs)Variable Index")
	     ("(elisp)Index")))

(info-lookup-maybe-add-help
 :mode 'lisp-interaction-mode
 :regexp "[^][()'\" \t\n]+"
 :parse-rule 'ignore

50451:fedb9513a26e

	      "`" "\\({[^}]*}\\)?'")))

(info-lookup-maybe-add-help
 :mode 'emacs-lisp-mode
 :regexp "[^][()'\" \t\n]+"
 :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
 :regexp "[^][()'\" \t\n]+"
 :parse-rule 'ignore