view lispref/index.texi @ 77114:b64b5f4be390

Merge from gnus--rel--5.10 Patches applied: * gnus--rel--5.10 (patch 214-215) - Merge from emacs--devo--0 - Update from CVS 2007-04-10 Katsumi Yamaoka <[e-mail]> * lisp/gnus/gnus-msg.el (gnus-inews-yank-articles): Use message-exchange-point-and-mark instead of exchange-point-and-mark. 2007-04-09 Katsumi Yamaoka <[e-mail]> * lisp/gnus/message.el (message-yank-original): Make sure cited text ends with newline; don't exchange point and mark. 2007-04-07 Chong Yidong <[e-mail]> * lisp/gnus/tls.el (open-tls-stream): Properly handle case where there is no associated buffer. Revision: [e-mail]/emacs--devo--0--patch-697

@c -*-texinfo-*-
@setfilename ../info/index

@c Indexing guidelines

@c I assume that all indexes will be combined.
@c Therefore, if a generated findex and permutations
@c cover the ways an index user would look up the entry,
@c then no cindex is added.
@c Concept index (cindex) entries will also be permuted.  Therefore, they
@c have no commas and few irrelevant connectives in them.

@c I tried to include words in a cindex that give the context of the entry,
@c particularly if there is more than one entry for the same concept.
@c For example, "nil in keymap"
@c Similarly for explicit findex and vindex entries, e.g. "print example".

@c Error codes are given cindex entries, e.g. "end-of-file error".

@c pindex is used for .el files and Unix programs

@node Index, , Standard Hooks, Top
@unnumbered Index

@c Print the indices

@printindex fn