@end defmac
The Common Lisp loop facility also contains features for working with
-iterators. See @xref{Loop Facility,,,cl,Common Lisp Extensions}.
+iterators. @xref{Loop Facility,,,cl,Common Lisp Extensions}.
The following piece of code demonstrates some important principles of
working with iterators.
A form that creates temporary bindings (@code{condition-case},
@code{dolist}, @code{dotimes}, @code{lambda}, @code{let}, or
@code{let*}), if all args are safe and the symbols to be bound are not
-explicitly risky (see @pxref{File Local Variables}).
+explicitly risky (@pxref{File Local Variables}).
@item
An assignment using @code{add-to-list}, @code{setq}, @code{push}, or
@code{pop}, if all args are safe and the symbols to be assigned are
@strong{Warning:} Do not design an element of @code{font-lock-keywords}
to match text which spans lines; this does not work reliably.
-For details, see @xref{Multiline Font Lock}.
+For details, @pxref{Multiline Font Lock}.
You can use @var{case-fold} in @code{font-lock-defaults} to specify
the value of @code{font-lock-keywords-case-fold-search} which says
terminate it, and @samp{\} quotes @samp{^}, @samp{-} or @samp{\}.
Thus, @code{"a-zA-Z"} skips over all letters, stopping before the
first nonletter, and @code{"^a-zA-Z"} skips nonletters stopping before
-the first letter. See @xref{Regular Expressions}. Character classes
-can also be used, e.g., @code{"[:alnum:]"}. See @pxref{Char Classes}.
+the first letter (@pxref{Regular Expressions}). Character classes
+can also be used, e.g., @code{"[:alnum:]"} (@pxref{Char Classes}).
If @var{limit} is supplied (it must be a number or a marker), it
specifies the maximum position in the buffer that point can be skipped
and so on.
You can configure the exact way comments get filled and broken, and
-where Emacs does auto-filling (see @pxref{Custom Filling and
+where Emacs does auto-filling (@pxref{Custom Filling and
Breaking}). Typically, the style system (@pxref{Styles}) will have
set this up for you, so you probably won't have to bother.
@end itemize
You can configure the precise circumstances in which newlines get
-inserted (see @pxref{Custom Auto-newlines}). Typically, the style
+inserted (@pxref{Custom Auto-newlines}). Typically, the style
system (@pxref{Styles}) will have set this up for you, so you probably
won't have to bother.
@comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
To configure macros which you invoke without a terminating @samp{;},
-see @xref{Macros with ;}.
+@pxref{Macros with ;}.
Here are the remaining odds and ends regarding indentation:
errors can be made visible when @code{dbus-debug} is set to @code{t}.
@end defspec
-Incoming D-Bus messages are handled as Emacs events, see @pxref{Misc
+Incoming D-Bus messages are handled as Emacs events, @pxref{Misc
Events, , , elisp}. They are retrieved only, when Emacs runs in
interactive mode. The generated event has this form:
@var{member} denote the message which has been sent.
@var{handler} is the callback function which has been registered for
-this message (see @pxref{Signals}). When a @code{dbus-event} event
+this message (@pxref{Signals}). When a @code{dbus-event} event
arrives, @var{handler} is called with @var{args} as arguments.
In order to inspect the @code{dbus-event} data, you could extend the
@code{find-file-other-window}. If you change this variable after
@file{dired-x.el} is loaded then do @kbd{M-x dired-x-bind-find-file}. The
default value of this variable is @code{t}; by default, the binding is not
-done. See @xref{Optional Installation File At Point}.
+done. @xref{Optional Installation File At Point}.
@item dired-x-bind-find-file
@findex dired-x-bind-find-file
that uses the value of @code{dired-x-hands-off-my-keys} to determine if
@code{dired-x-find-file} should be bound over @code{find-file} and
@code{dired-x-find-file-other-window} bound over
-@code{find-file-other-window}. See @xref{Optional Installation File At Point}.
+@code{find-file-other-window}. @xref{Optional Installation File At Point}.
@end table
@node Miscellaneous Commands
display.
@end defvar
-This variable has protocol-local definitions (see @pxref{Server/Protocol
+This variable has protocol-local definitions (@pxref{Server/Protocol
Locals}). For instance, it is defined as follows for LDAP:
@lisp
@var{format}s are in fact not limited to EUDC attribute names, you can
use server or protocol specific names in them. It may be safer if you
do so, to set the variable @code{eudc-inline-query-format} in a protocol
-or server local fashion (see @pxref{Server/Protocol Locals}).
+or server local fashion (@pxref{Server/Protocol Locals}).
For instance you could use the following to match up to three words
against the @code{cn} attribute of LDAP servers:
Yes, if the POP3 server supports the UIDL control (maybe almost servers
do it nowadays). To do that, add a @code{:leave VALUE} pair to each
-POP3 mail source. See @pxref{Mail Source Specifiers} for VALUE.
+POP3 mail source. @xref{Mail Source Specifiers}, for details on VALUE.
@node FAQ 4 - Reading messages
@subsection Reading messages
(sieve header :regex "list-id" "<c++std-\\1.accu.org>")
@end example
-See @pxref{Sieve Commands} for commands and variables that might be of
+@xref{Sieve Commands}, for commands and variables that might be of
interest in relation to the sieve parameter.
The Sieve language is described in RFC 3028. @xref{Top, Emacs Sieve,
expression, or if it takes the form @code{(header @var{match}
@var{regexp})}, a @samp{gnus-match-substitute-replacement} is proceed
on the value to replace the positional parameters @samp{\@var{n}} by
-the corresponding parenthetical matches (see @xref{Replacing Match,,
+the corresponding parenthetical matches (@pxref{Replacing Match,,
Replacing the Text that Matched, elisp, The Emacs Lisp Reference
Manual}.)
Do not skip, speed-read, or glance through this section.
Make sure you read the section on the @code{spam.el} sequence of
-events. See @xref{Extending the Spam package}.
+events. @xref{Extending the Spam package}.
@cindex spam-initialize
@vindex spam-use-stat
these for several export back-ends. When exporting to @LaTeX{}, the code is
left as it is. When exporting to HTML, Org can use either
@uref{http://www.mathjax.org, MathJax} (@pxref{Math formatting in HTML
-export}) or transcode the math into images (see @pxref{Previewing @LaTeX{}
+export}) or transcode the math into images (@pxref{Previewing @LaTeX{}
fragments}).
@LaTeX{} fragments don't need any special marking at all. The following
and from the @file{imagemagick} suite. Choose the converter by setting the
variable @code{org-preview-latex-default-process} accordingly.}, @LaTeX{}
fragments can be processed to produce images of the typeset expressions to be
-used for inclusion while exporting to HTML (see @pxref{@LaTeX{} fragments}),
+used for inclusion while exporting to HTML (@pxref{@LaTeX{} fragments}),
or for inline previewing within Org mode.
@vindex org-format-latex-options
Here is a summary of @RefTeX{}'s commands which can be executed from
@LaTeX{} files. Command which are executed from the special buffers are
not described here. All commands are available from the @code{Ref}
-menu. See @xref{Key Bindings}.
+menu. @xref{Key Bindings}.
@deffn Command reftex-toc
Show the table of contents for the current document. When called with
projects / emacs.git / commitdiff