[Q21.5QR21.4] Make the definition of what a command is more accessible in Lispref.
QUERY 21.5 QUERY RECOMMEND 21.4
Thanks for the patch, but renaming the _node_ will make it more
useful, enough to be worth the extra work.
Vin: this should definitely go into 21.4.17, but needs some changes first.
2005-01-18 Aidan Kehoe <kehoea(a)parhasard.net>
* lispref/functions.texi (Functions): Rename to "Functions and
Commands"
* lispref/functions.texi (What Is a Function): Move the definition
of a command further up the list, give information on a trivial
(interactive) declaration, and cross-reference to the key binding
detail. Cf. 87vf9wgd08.fsf(a)tleepslib.sk.tsukuba.ac.jp
(comp.emacs.xemacs, 2005-01-18).
Aidan> Index: man/lispref/functions.texi
Aidan> ＠＠ -4,7 +4,7 ＠＠
Aidan> ＠c See the file lispref.texi for copying conditions.
Aidan> ＠setfilename ../../info/functions.info
Aidan> ＠node Functions, Macros, Variables, Top
Aidan> -＠chapter Functions
Aidan> +＠chapter Functions and Commands
You should change the node name as well; the chapter name does not
appear in menus and cross-references.
Aidan> +A ＠dfn{command} is a possible definition for a key sequence---we count
Aidan> +mouse events and menu accesses as key sequences for this purpose. More
Aidan> +formally, within XEmacs lisp, a command is something that
Aidan> +＠code{command-execute} can invoke.
Well-written, thanks!
Aidan> +completion, see ＠pxref{Defining Commands}. Such a function can be
and
Aidan> +do this, see ＠pxref{Key Binding Commands}.
will produce "see see" in the output AFAIK. These should be ＠refs.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.