Fix some doc/ cross-references
* doc/lispintro/emacs-lisp-intro.texi (edebug): * doc/lispref/debugging.texi (Debugging): * doc/lispref/files.texi (File Attributes, Changing Files): * doc/misc/bovine.texi (top): * doc/misc/cc-mode.texi (AWK Mode Font Locking): * doc/misc/mh-e.texi (Preface): * doc/misc/url.texi (URI Parsing): Fix cross-references to other manuals. * doc/lispref/package.texi (Package Archives): Fix @url call.
This commit is contained in:
parent
0946b7cade
commit
a944db142f
11 changed files with 29 additions and 11 deletions
|
@ -1,3 +1,7 @@
|
|||
2013-07-03 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* emacs-lisp-intro.texi (edebug): Fix cross-references.
|
||||
|
||||
2013-03-12 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* emacs-lisp-intro.texi: Add some stuff specific to www.gnu.org.
|
||||
|
|
|
@ -18619,7 +18619,7 @@ shows which line you are currently executing.
|
|||
You can walk through the execution of a function, line by line, or run
|
||||
quickly until reaching a @dfn{breakpoint} where execution stops.
|
||||
|
||||
Edebug is described in @ref{edebug, , Edebug, elisp, The GNU Emacs
|
||||
Edebug is described in @ref{Edebug, , , elisp, The GNU Emacs
|
||||
Lisp Reference Manual}.
|
||||
|
||||
@need 1250
|
||||
|
@ -18746,7 +18746,7 @@ error or at specified stopping points; you can cause it to display the
|
|||
changing values of various expressions; you can find out how many
|
||||
times a function is called, and more.
|
||||
|
||||
Edebug is described in @ref{edebug, , Edebug, elisp, The GNU Emacs
|
||||
Edebug is described in @ref{Edebug, , , elisp, The GNU Emacs
|
||||
Lisp Reference Manual}.
|
||||
|
||||
@need 1500
|
||||
|
|
|
@ -1,3 +1,10 @@
|
|||
2013-07-03 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* debugging.texi (Debugging):
|
||||
* files.texi (File Attributes, Changing Files): Fix cross-references.
|
||||
|
||||
* package.texi (Package Archives): Fix @url call.
|
||||
|
||||
2013-06-26 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* syntax.texi (Syntax Table Functions): Mention describe-syntax.
|
||||
|
|
|
@ -32,7 +32,7 @@ program.
|
|||
|
||||
@item
|
||||
You can use the ERT package to write regression tests for the program.
|
||||
@xref{Top,the ERT manual,, ERT, ERT: Emacs Lisp Regression Testing}.
|
||||
@xref{Top,the ERT manual,, ert, ERT: Emacs Lisp Regression Testing}.
|
||||
|
||||
@item
|
||||
You can profile the program to get hints about how to make it more efficient.
|
||||
|
|
|
@ -1112,7 +1112,7 @@ permissions} of @var{filename}, as an integer. It recursively follows
|
|||
symbolic links in @var{filename} at all levels. If @var{filename}
|
||||
does not exist, the return value is @code{nil}.
|
||||
|
||||
@xref{File Permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
|
||||
@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
|
||||
Manual}, for a description of mode bits. If the low-order bit is 1,
|
||||
then the file is executable by all users, if the second-lowest-order
|
||||
bit is 1, then the file is writable by all users, etc. The highest
|
||||
|
@ -1599,7 +1599,7 @@ octal numbers to enter @var{mode}. For example,
|
|||
@noindent
|
||||
specifies that the file should be readable and writable for its owner,
|
||||
readable for group members, and readable for all other users.
|
||||
@xref{File Permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
|
||||
@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
|
||||
Manual}, for a description of mode bit specifications.
|
||||
|
||||
Interactively, @var{mode} is read from the minibuffer using
|
||||
|
@ -1650,7 +1650,7 @@ the permissions on which the specification is based are taken from the
|
|||
mode bits of @var{base-file}. If @var{base-file} is omitted or
|
||||
@code{nil}, the function uses @code{0} as the base mode bits. The
|
||||
complete and relative specifications can be combined, as in
|
||||
@code{"u+r,g+rx,o+r,g-w"}. @xref{File Permissions,,, coreutils, The
|
||||
@code{"u+r,g+rx,o+r,g-w"}. @xref{File permissions,,, coreutils, The
|
||||
@sc{gnu} @code{Coreutils} Manual}, for a description of file mode
|
||||
specifications.
|
||||
@end defun
|
||||
|
|
|
@ -265,7 +265,7 @@ variable @code{load-file-name} (@pxref{Loading}). Here is an example:
|
|||
Via the Package Menu, users may download packages from @dfn{package
|
||||
archives}. Such archives are specified by the variable
|
||||
@code{package-archives}, whose default value contains a single entry:
|
||||
the archive hosted by the GNU project at @url{elpa.gnu.org}. This
|
||||
the archive hosted by the GNU project at @url{http://elpa.gnu.org}. This
|
||||
section describes how to set up and maintain a package archive.
|
||||
|
||||
@cindex base location, package archive
|
||||
|
|
|
@ -1,3 +1,10 @@
|
|||
2013-07-03 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* bovine.texi (top):
|
||||
* cc-mode.texi (AWK Mode Font Locking):
|
||||
* mh-e.texi (Preface):
|
||||
* url.texi (URI Parsing): Fix cross-references to other manuals.
|
||||
|
||||
2013-06-24 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* eshell.texi: Fix cross-references to other manuals.
|
||||
|
|
|
@ -76,7 +76,7 @@ The @dfn{bovine} parser is the original @semantic{} parser, and is an
|
|||
implementation of an @acronym{LL} parser. It is good for simple
|
||||
languages. It has many conveniences making grammar writing easy. The
|
||||
conveniences make it less powerful than a Bison-like @acronym{LALR}
|
||||
parser. For more information, @inforef{top, the Wisent Parser Manual,
|
||||
parser. For more information, @inforef{Top, The Wisent Parser Manual,
|
||||
wisent}.
|
||||
|
||||
Bovine @acronym{LL} grammars are stored in files with a @file{.by}
|
||||
|
|
|
@ -2111,7 +2111,7 @@ contributing it: send a note to @email{bug-cc-mode@@gnu.org}.
|
|||
@comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
||||
|
||||
The general appearance of font-locking in AWK mode is much like in any
|
||||
other programming mode. @xref{Faces For Font Lock,,,elisp, GNU Emacs
|
||||
other programming mode. @xref{Faces for Font Lock,,,elisp, GNU Emacs
|
||||
Lisp Reference Manual}.
|
||||
|
||||
The following faces are, however, used in a non-standard fashion in
|
||||
|
|
|
@ -233,7 +233,7 @@ read an online tutorial by starting GNU Emacs and typing @kbd{C-h t}
|
|||
@cite{GNU Emacs Manual},
|
||||
@end iftex
|
||||
@ifinfo
|
||||
@ref{top, , GNU Emacs Manual, emacs, GNU Emacs Manual},
|
||||
@ref{Top, , GNU Emacs Manual, emacs, GNU Emacs Manual},
|
||||
@end ifinfo
|
||||
@ifhtml
|
||||
@uref{http://www.gnu.org/software/emacs/manual/html_node/,
|
||||
|
|
|
@ -138,7 +138,7 @@ Given a parsed URI, this function returns the corresponding URI string.
|
|||
The return value of @code{url-generic-parse-url}, and the argument
|
||||
expected by @code{url-recreate-url}, is a @dfn{parsed URI}: a CL
|
||||
structure whose slots hold the various components of the URI@.
|
||||
@xref{top,the CL Manual,,cl,GNU Emacs Common Lisp Emulation}, for
|
||||
@xref{Top,the CL Manual,,cl,GNU Emacs Common Lisp Emulation}, for
|
||||
details about CL structures. Most of the other functions in the
|
||||
@code{url} library act on parsed URIs.
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue