@c -*-texinfo-*-
@c This is part of the GNU Emacs Lisp Reference Manual.
-@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
-@c Free Software Foundation, Inc.
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2002, 2003,
+@c 2004, 2005 Free Software Foundation, Inc.
@c See the file elisp.texi for copying conditions.
@setfilename ../info/help
@node Documentation, Files, Modes, Top
string follows the argument list. In a variable definition, the
documentation string follows the initial value of the variable.
- When you write a documentation string, make the first line a complete
-sentence (or two complete sentences) since some commands, such as
-@code{apropos}, show only the first line of a multi-line documentation
-string. Also, you should not indent the second line of a documentation
-string, if it has one, because that looks odd when you use @kbd{C-h f}
-(@code{describe-function}) or @kbd{C-h v} (@code{describe-variable}) to
-view the documentation string. @xref{Documentation Tips}.
+ When you write a documentation string, make the first line a
+complete sentence (or two complete sentences) since some commands,
+such as @code{apropos}, show only the first line of a multi-line
+documentation string. Also, you should not indent the second line of
+a documentation string, if it has one, because that looks odd when you
+use @kbd{C-h f} (@code{describe-function}) or @kbd{C-h v}
+(@code{describe-variable}) to view the documentation string. There
+are many other conventions for doc strings; see @ref{Documentation
+Tips}.
Documentation strings can contain several special substrings, which
stand for key bindings to be looked up in the current keymaps when the
documentation is displayed. This allows documentation strings to refer
to the keys for related commands and be accurate even when a user
-rearranges the key bindings. (@xref{Accessing Documentation}.)
+rearranges the key bindings. (@xref{Keys in Documentation}.)
In Emacs Lisp, a documentation string is accessible through the
function or variable that it describes:
@itemize @bullet
@item
-The documentation for a function is stored in the function definition
-itself (@pxref{Lambda Expressions}). The function @code{documentation}
-knows how to extract it.
+@kindex function-documentation
+The documentation for a function is usually stored in the function
+definition itself (@pxref{Lambda Expressions}). The function
+@code{documentation} knows how to extract it. You can also put
+function documentation in the @code{function-documentation} property
+of the function name. That is useful with definitions such as
+keyboard macros that can't hold a documentation string.
@item
@kindex variable-documentation
property value isn't @code{nil}, isn't a string, and doesn't refer to
text in a file, then it is evaluated to obtain a string.
-Finally, @code{documentation-property} passes the string through
+The last thing this function does is pass the string through
@code{substitute-command-keys} to substitute actual key bindings,
unless @var{verbatim} is non-@code{nil}.
@code{documentation-property}, to display the documentation strings for
several symbols in a @samp{*Help*} buffer.
+@anchor{describe-symbols example}
@smallexample
@group
(defun describe-symbols (pattern)
in the `*Help*' buffer."
(interactive "sDescribe symbols matching: ")
(let ((describe-func
- (function
+ (function
(lambda (s)
@end group
@group
(if (fboundp s) ; @r{It is a function.}
(princ
(format "%s\t%s\n%s\n\n" s
- (if (commandp s)
+ (if (commandp s)
(let ((keys (where-is-internal s)))
(if keys
(concat
"Keys: "
- (mapconcat 'key-description
+ (mapconcat 'key-description
keys " "))
"Keys: none"))
"Function")
@end group
@group
- (or (documentation s)
+ (or (documentation s)
"not documented"))))
-
+
(if (boundp s) ; @r{It is a variable.}
@end group
@group
(princ
(format "%s\t%s\n%s\n\n" s
- (if (user-variable-p s)
+ (if (user-variable-p s)
"Option " "Variable")
@end group
@group
- (or (documentation-property
+ (or (documentation-property
s 'variable-documentation)
"not documented")))))))
sym-list)
@group
;; @r{Build a list of symbols that match pattern.}
- (mapatoms (function
+ (mapatoms (function
(lambda (sym)
(if (string-match pattern (symbol-name sym))
(setq sym-list (cons sym sym-list))))))
(describe-symbols "goal")
---------- Buffer: *Help* ----------
-goal-column Option
+goal-column Option
*Semipermanent goal column for vertical motion, as set by @dots{}
@end group
@c Do not blithely break or fill these lines.
Variables}.
@defun Snarf-documentation filename
+@anchor{Definition of Snarf-documentation}
This function is used only during Emacs initialization, just before
the runnable Emacs is dumped. It finds the file offsets of the
documentation strings stored in the file @var{filename}, and records
In most cases, this is the same as @code{data-directory}. They may be
different when you run Emacs from the directory where you built it,
-without actually installing it. See @code{data-directory} in @ref{Help
-Functions}.
+without actually installing it. @xref{Definition of data-directory}.
In older Emacs versions, @code{exec-directory} was used for this.
@end defvar
stands for a key sequence that will invoke @var{command}, or @samp{M-x
@var{command}} if @var{command} has no key bindings.
-@item \@{@var{mapvar}@}
+@item \@{@var{mapvar}@}
stands for a summary of the keymap which is the value of the variable
@var{mapvar}. The summary is made using @code{describe-bindings}.
-@item \<@var{mapvar}>
+@item \<@var{mapvar}>
stands for no text itself. It is used only for a side effect: it
specifies @var{mapvar}'s value as the keymap for any following
@samp{\[@var{command}]} sequences in this documentation string.
@smallexample
@group
-(substitute-command-keys
+(substitute-command-keys
"To abort recursive edit, type: \\[abort-recursive-edit]")
@result{} "To abort recursive edit, type: C-]"
@end group
@group
-(substitute-command-keys
+(substitute-command-keys
"The keys that are defined for the minibuffer here are:
\\@{minibuffer-local-must-match-map@}")
@result{} "The keys that are defined for the minibuffer here are:
characters. The description of a non-whitespace printing character is
the character itself.
-@defun key-description sequence
+@defun key-description sequence &optional prefix
@cindex Emacs event standard notation
This function returns a string containing the Emacs standard notation
-for the input events in @var{sequence}. The argument @var{sequence} may
-be a string, vector or list. @xref{Input Events}, for more information
-about valid events. See also the examples for
-@code{single-key-description}, below.
+for the input events in @var{sequence}. If @var{prefix} is
+non-@code{nil}, it is a sequence of input events leading up to
+@var{sequence} and is included in the return value. Both arguments
+may be strings, vectors or lists. @xref{Input Events}, for more
+information about valid events.
+
+@smallexample
+@group
+(key-description [?\M-3 delete])
+ @result{} "M-3 <delete>"
+@end group
+@group
+(key-description [delete] "\M-3")
+ @result{} "M-3 <delete>"
+@end group
+@end smallexample
+
+ See also the examples for @code{single-key-description}, below.
@end defun
@defun single-key-description event &optional no-angles
standard Emacs notation for characters that appear in text---like
@code{single-key-description}, except that control characters are
represented with a leading caret (which is how control characters in
-Emacs buffers are usually displayed).
+Emacs buffers are usually displayed). Another difference is that
+@code{text-char-description} recognizes the 2**7 bit as the Meta
+character, whereas @code{single-key-description} uses the 2**27 bit
+for Meta.
@smallexample
@group
@end group
@group
(text-char-description ?\M-m)
- @result{} "M-m"
+ @result{} "\xed"
@end group
@group
(text-char-description ?\C-\M-m)
+ @result{} "\x8d"
+@end group
+@group
+(text-char-description (+ 128 ?m))
+ @result{} "M-m"
+@end group
+@group
+(text-char-description (+ 128 ?\C-m))
@result{} "M-^M"
@end group
@end smallexample
@end defun
-@defun read-kbd-macro string
+@defun read-kbd-macro string &optional need-vector
This function is used mainly for operating on keyboard macros, but it
can also be used as a rough inverse for @code{key-description}. You
call it with a string containing key descriptions, separated by spaces;
it returns a string or vector containing the corresponding events.
(This may or may not be a single valid key sequence, depending on what
-events you use; @pxref{Keymap Terminology}.)
+events you use; @pxref{Keymap Terminology}.) If @var{need-vector} is
+non-@code{nil}, the return value is always a vector.
@end defun
@node Help Functions
we describe some program-level interfaces to the same information.
@deffn Command apropos regexp &optional do-all
-This function finds all symbols whose names contain a match for the
-regular expression @var{regexp}, and returns a list of them
-(@pxref{Regular Expressions}). It also displays the symbols in a buffer
-named @samp{*Help*}, each with a one-line description taken from the
-beginning of its documentation string.
+This function finds all ``meaningful'' symbols whose names contain a
+match for the regular expression @var{regexp}, and returns a list of
+them, with associated documentation (@pxref{Regular Expressions}). It
+also displays the symbols in a buffer named @samp{*Apropos*}, each
+with a one-line description taken from the beginning of its
+documentation string. A symbol is ``meaningful'' if it has a
+definition as a function, variable, or face, or has properties.
@c Emacs 19 feature
-If @var{do-all} is non-@code{nil}, then @code{apropos} also shows key
-bindings for the functions that are found; it also shows all symbols,
-even those that are neither functions nor variables.
-
-In the first of the following examples, @code{apropos} finds all the
-symbols with names containing @samp{exec}. (We don't show here the
-output that results in the @samp{*Help*} buffer.)
-
-@smallexample
-@group
-(apropos "exec")
- @result{} (Buffer-menu-execute command-execute exec-directory
- exec-path execute-extended-command execute-kbd-macro
- executing-kbd-macro executing-macro)
-@end group
-@end smallexample
+If @var{do-all} is non-@code{nil}, or if the user option
+@code{apropos-do-all} is non-@code{nil}, then @code{apropos} also
+shows key bindings for the functions that are found; it also shows
+@emph{all} interned symbols, not just meaningful ones (and it lists
+them in the return value as well).
@end deffn
@defvar help-map
@smallexample
@group
-(define-key global-map "\C-h" 'help-command)
+(define-key global-map (char-to-string help-char) 'help-command)
(fset 'help-command help-map)
@end group
@end smallexample
string that explains what the input is for and how to enter it properly.
Entry to the minibuffer binds this variable to the value of
-@code{minibuffer-help-form} (@pxref{Minibuffer Misc}).
+@code{minibuffer-help-form} (@pxref{Definition of minibuffer-help-form}).
@end defvar
@defvar prefix-help-command
@c Emacs 19 feature
@defvar data-directory
+@anchor{Definition of data-directory}
This variable holds the name of the directory in which Emacs finds
certain documentation and text files that come with Emacs. In older
Emacs versions, @code{exec-directory} was used for this.
@c Emacs 19 feature
@defmac make-help-screen fname help-line help-text help-map
-This macro defines a help command named @var{fname} that acts like a
+This macro defines a help command named @var{fname} that acts like a
prefix key that shows a list of the subcommands it offers.
When invoked, @var{fname} displays @var{help-text} in a window, then
echo area at first, and display the longer @var{help-text} strings only
if the user types the help character again.
@end defopt
+
+@ignore
+ arch-tag: ba36b4c2-e60f-49e2-bc25-61158fdcd815
+@end ignore