From: Xue Fuqiao Date: Fri, 3 Jul 2015 03:21:08 +0000 (+0800) Subject: Add cross references in documentation X-Git-Tag: emacs-25.0.90~1573 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=2b848fadd51e805b2f46da64c5958ea7f009048a;p=emacs.git Add cross references in documentation * doc/emacs/display.texi (Displaying Boundaries): * doc/emacs/search.texi (Word Search): Add cross references. --- diff --git a/doc/emacs/display.texi b/doc/emacs/display.texi index bed25a5b7ce..601a40bd176 100644 --- a/doc/emacs/display.texi +++ b/doc/emacs/display.texi @@ -1112,13 +1112,14 @@ how the buffer boundaries and window scrolling is indicated in the fringes. If the value is @code{left} or @code{right}, both angle and arrow bitmaps are displayed in the left or right fringe, respectively. - If value is an alist, each element @code{(@var{indicator} . -@var{position})} specifies the position of one of the indicators. -The @var{indicator} must be one of @code{top}, @code{bottom}, -@code{up}, @code{down}, or @code{t} which specifies the default -position for the indicators not present in the alist. -The @var{position} is one of @code{left}, @code{right}, or @code{nil} -which specifies not to show this indicator. + If value is an alist (@pxref{Association Lists,,, elisp, the Emacs +Lisp Reference Manual}), each element @code{(@var{indicator} . +@var{position})} specifies the position of one of the indicators. The +@var{indicator} must be one of @code{top}, @code{bottom}, @code{up}, +@code{down}, or @code{t} which specifies the default position for the +indicators not present in the alist. The @var{position} is one of +@code{left}, @code{right}, or @code{nil} which specifies not to show +this indicator. For example, @code{((top . left) (t . right))} places the top angle bitmap in left fringe, the bottom angle bitmap in right fringe, and diff --git a/doc/emacs/search.texi b/doc/emacs/search.texi index b69146a992a..247033d4353 100644 --- a/doc/emacs/search.texi +++ b/doc/emacs/search.texi @@ -511,8 +511,8 @@ the search string must exactly match a whole word. In an incremental word search, the matching is more lax: while you are typing the search string, its first and last words need not match whole words. This is so that the matching can proceed incrementally as you type. This -additional laxity does not apply to the lazy highlight, which always -matches whole words. +additional laxity does not apply to the lazy highlight +(@pxref{Incremental Search}), which always matches whole words. @node Symbol Search @section Symbol Search