hrp@earth.cray.com (Hal Peterson) (02/02/89)
Here are some changes I made to get texinfo to stop complaining about the
cross-references in the Elisp manual. Trivial stuff, but somebody has to
do the gruntwork.
*** buffer-local.texinfo~ Tue Sep 13 12:37:41 1988
--- buffer-local.texinfo Wed Feb 1 12:38:48 1989
***************
*** 29,35 ****
@pxref{overwrite-mode}
@item abbrev-mode
! @pxref{Abbrev Mode}
@item tab-width
@pxref{tab-width}
--- 29,35 ----
@pxref{overwrite-mode}
@item abbrev-mode
! @pxref{Abbrev Mode, , Abbrev Mode, emacs, GNU Emacs User Manual}
@item tab-width
@pxref{tab-width}
***************
*** 41,47 ****
@pxref{case-fold-search}
@item left-margin
! @pxref{Left Margin}
@item local-abbrev-table
@pxref{local-abbrev-table}
--- 41,47 ----
@pxref{case-fold-search}
@item left-margin
! @pxref{Left Margin, , Left Margin, emacs, GNU Emacs User Manual}
@item local-abbrev-table
@pxref{local-abbrev-table}
*** keymaps.texinfo~ Wed Feb 1 12:06:33 1989
--- keymaps.texinfo Wed Feb 1 12:23:27 1989
***************
*** 275,281 ****
If @var{firstonly} is non-@code{nil}, then it returns a string representing the
first key sequence found, rather than a list of all possible key sequences.
! This function is used by @code{where-is} (see the GNU Emacs User Manual).
@example
(where-is-internal 'forward-char)
@b{=>} ("^F")
--- 275,281 ----
If @var{firstonly} is non-@code{nil}, then it returns a string representing the
first key sequence found, rather than a list of all possible key sequences.
! This function is used by @code{where-is} (@pxref{Help, , Help, emacs, GNU Emacs User Manual}).
@example
(where-is-internal 'forward-char)
@b{=>} ("^F")
*** minibuffer.texinfo~ Wed Sep 14 01:24:22 1988
--- minibuffer.texinfo Wed Feb 1 12:24:15 1989
***************
*** 21,27 ****
from Emacs are displayed, using @code{message} or something similar.
The User Manual specifies the rules for how conflicts between
use of the echo and the minibuffer are resolved
! (@pxref{Minibuffer,Emacs User Manual}).
The minibuffer is a true buffer; editing commands work there, for
instance.
--- 21,27 ----
from Emacs are displayed, using @code{message} or something similar.
The User Manual specifies the rules for how conflicts between
use of the echo and the minibuffer are resolved
! (@pxref{Minibuffer, , The Minibuffer, emacs, GNU Emacs User Manual}).
The minibuffer is a true buffer; editing commands work there, for
instance.
*** sequences.texinfo~ Wed Sep 14 00:47:39 1988
--- sequences.texinfo Wed Feb 1 12:04:43 1989
***************
*** 118,124 ****
The elements of a @dfn{string} must
be characters (i.e., integers between 0 and 255). Strings are covered
! in a separate chapter (@pxref{Strings}).
@node
--- 118,124 ----
The elements of a @dfn{string} must
be characters (i.e., integers between 0 and 255). Strings are covered
! in a separate chapter (@pxref{Strings and Characters}).
@node
*** windows.texinfo~ Wed Feb 1 12:35:01 1989
--- windows.texinfo Wed Feb 1 14:13:27 1989
***************
*** 226,232 ****
@var{window}. If @var{minibuf} is @code{t}, then the canonical ordering
includes the minibuffer window even if it is not active. If @var{minibuf}
is neither @code{t} nor @code{nil}, then the minibuffer window is not
! included even if it is active. @xref{Minibuffer} for what it means
for the minibuffer to be active.
In the example, there are two windows in existence. They both happen to
--- 226,233 ----
@var{window}. If @var{minibuf} is @code{t}, then the canonical ordering
includes the minibuffer window even if it is not active. If @var{minibuf}
is neither @code{t} nor @code{nil}, then the minibuffer window is not
! included even if it is active. @xref{Minibuffer,, Minibuffer, emacs,
! GNU Emacs User Manual} for what it means
for the minibuffer to be active.
In the example, there are two windows in existence. They both happen to