The user can add any key matching the specified key type, but you can
give some keys a preferential treatment by specifying them with the
-@code{:options} (@pxref{Variable Definitions}). The specified keys
+@code{:options} (see @ref{Variable Definitions}). The specified keys
will always be shown in the customize buffer (together with a suitable
value), with a checkbox to include or exclude or disable the key/value
pair from the alist. The user will not be able to edit the keys
indirect specifications.
Here's a table of the possible elements of a specification list, with
-their meanings (@pxref{Specification Examples}, for the referenced
+their meanings (see @ref{Specification Examples}, for the referenced
examples):
@table @code
@cindex evaluation error
@cindex infinite recursion
This variable defines the limit on the total number of local variable
-bindings and @code{unwind-protect} cleanups (@pxref{Cleanups,,
+bindings and @code{unwind-protect} cleanups (see @ref{Cleanups,,
Cleaning Up from Nonlocal Exits}) that are allowed before Emacs
signals an error (with data @code{"Variable binding depth exceeds
max-specpdl-size"}).
@item
@key{DEL}: @key{Delete}, usually @strong{not} the same as
-@key{Backspace}; same as @kbd{C-?} (@pxref{Backspace invokes help}, if
+@key{Backspace}; same as @kbd{C-?} (see @ref{Backspace invokes help}, if
deleting invokes Emacs help)
@item
are available for you to read.
The following files (and others) are available in the @file{etc}
-directory of the Emacs distribution (@pxref{File-name conventions}, if
+directory of the Emacs distribution (see @ref{File-name conventions}, if
you're not sure where that is). Many of these files are available via
the Emacs @samp{Help} menu, or by typing @kbd{C-h ?} (@kbd{M-x
help-for-help}).
For @file{file.h}, the include directives to look for are
@code{#include "file.h"}, @code{#include "../file.h"}, etc. Each
include is checked against a list of include directories
-(@pxref{Getting the include directories}) to be sure it points to the
+(see @ref{Getting the include directories}) to be sure it points to the
correct @file{file.h}.
First matching master file found stops the search. The master file is then
@dfn{groups}, and @dfn{articles}. Servers can be local or remote.
Each server maintains a list of groups, and those groups contain
articles. Because Gnus presents a unified interface to a wide variety
-of servers, the vocabulary doesn't always quite line up (@pxref{FAQ
+of servers, the vocabulary doesn't always quite line up (see @ref{FAQ
- Glossary}, for a more complete glossary). Thus a local maildir is
referred to as a ``server'' (@pxref{Finding the News}) the same as a
Usenet or IMAP server is; ``groups'' (@pxref{Group Buffer}) might mean
@item
Dired integration
-@code{gnus-dired-minor-mode} (@pxref{Other modes}) installs key
+@code{gnus-dired-minor-mode} (see @ref{Other modes}) installs key
bindings in dired buffers to send a file as an attachment, open a file
using the appropriate mailcap entry, and print a file using the mailcap
entry.
(hfy-flatten-style @var{style})
@end lisp
-Take @var{style} (@pxref{hfy-face-to-style-i}, @pxref{hfy-face-to-style})
+Take @var{style} (see @ref{hfy-face-to-style-i}, @ref{hfy-face-to-style})
and merge any multiple attributes appropriately. Currently only font-size is
merged down to a single occurrence---others may need special handling, but I
haven't encountered them yet. Returns a @ref{hfy-style-assoc}.
@end lisp
Find face in effect at point P@. If overlays are to be considered
-(@pxref{hfy-optimizations}) then this may return a @code{defface} style
+(see @ref{hfy-optimizations}) then this may return a @code{defface} style
list of face properties instead of a face symbol.
@item hfy-bgcol
Read HTML messages (@pxref{HTML}).
@c -------------------------
@item
-Use aliases and identities (@pxref{Aliases}, @pxref{Identities}).
+Use aliases and identities (see @ref{Aliases}, @pxref{Identities}).
@c -------------------------
@item
-Create different views of your mail (@pxref{Threading}, @pxref{Limits}).
+Create different views of your mail (see @ref{Threading}, @pxref{Limits}).
@c -------------------------
@item
Deal with junk mail (@pxref{Junk}).
@c -------------------------
@item
-Handle signed and encrypted messages (@pxref{Reading PGP},
+Handle signed and encrypted messages (see @ref{Reading PGP},
@pxref{Sending PGP}).
@c -------------------------
@item
Use sequences conveniently (@pxref{Sequences}).
@c -------------------------
@item
-Use the speedbar, tool bar, and menu bar (@pxref{Speedbar}, @pxref{Tool
+Use the speedbar, tool bar, and menu bar (see @ref{Speedbar}, see @ref{Tool
Bar}, @pxref{Menu Bar}).
@c -------------------------
@item
Most commands in PCL-CVS require that you have a @file{*cvs*}
buffer. The commands that you use to get one are listed below.
For each, a @samp{cvs} process will be run, the output will be parsed by
-PCL-CVS, and the result will be printed in the @file{*cvs*} buffer
-(@pxref{Buffer contents}, for a description of the buffer's contents).
+PCL-CVS, and the result will be printed in the @file{*cvs*} buffer (see
+@ref{Buffer contents}, for a description of the buffer's contents).
@table @kbd
@item M-x cvs-update
indication that the process has been interrupted, and returns a
corresponding string.
-This remote process handling does not apply to @acronym{GVFS}
-(@pxref{GVFS-based methods}) because the remote file system is mounted on
+This remote process handling does not apply to @acronym{GVFS} (see
+@ref{GVFS-based methods}) because the remote file system is mounted on
the local host and @value{tramp} accesses it by changing the
@code{default-directory}.
For @value{tramp} to find the command on the remote, it must be
accessible through the default search path as setup by @value{tramp}
upon first connection. Alternatively, use an absolute path or extend
-@code{tramp-remote-path} (@pxref{Remote programs}):
+@code{tramp-remote-path} (see @ref{Remote programs}):
@lisp
@group
@vindex vhdl-offsets-alist
@vindex offsets-alist @r{(vhdl-)}
Indentation for the current line is calculated using the syntactic
-component list derived in step 1 above (@pxref{Syntactic
+component list derived in step 1 above (see @ref{Syntactic
Analysis}). Each component contributes to the final total indentation
of the line in two ways.
@cindex custom indentation functions
One of the most common ways to customize VHDL Mode is by writing
@dfn{custom indentation functions} and associating them with specific
-syntactic symbols (@pxref{Syntactic Symbols}). VHDL Mode itself
+syntactic symbols (see @ref{Syntactic Symbols}). VHDL Mode itself
uses custom indentation functions to provide more sophisticated
indentation, for example when lining up selected signal assignments:
@example
@end example
@noindent
Custom indent functions take a single argument, which is a syntactic
-component cons cell (@pxref{Syntactic Analysis}). The
+component cons cell (see @ref{Syntactic Analysis}). The
function returns an integer offset value that will be added to the
running total indentation for the line. Note that what actually gets
returned is the difference between the column that the signal assignment