annotate lispref/index.texi @ 71224:b7261e09f8e4

* cc-mode.texi (Getting Started, Indentation Commands, Config Basics) (Custom Filling and Breaking, Custom Braces, Syntactic Symbols) (Line-Up Functions, Custom Macros): * ediff.texi (Window and Frame Configuration) (Highlighting Difference Regions, Highlighting Difference Regions): * emacs-mime.texi (Display Customization): * erc.texi (History): * eshell.texi (Known problems): * eudc.texi (Overview, BBDB): * gnus.texi (NNTP, IMAP, Advanced Scoring Examples) (The problem of spam, SpamOracle, Extending the Spam package) (Conformity, Terminology): * idlwave.texi (Routine Info, Routine Info) (Class and Keyword Inheritance, Padding Operators) (Breakpoints and Stepping, Electric Debug Mode) (Examining Variables, Troubleshooting): * org.texi (Creating timestamps): * reftex.texi (Commands, Options, Changes): * tramp.texi (Inline methods, Password caching) (Auto-save and Backup, Issues): * vip.texi (Files, Commands in Insert Mode): * viper.texi (Emacs Preliminaries, States in Viper) (Packages that Change Keymaps, Viper Specials, Groundwork): * xresmini.texi (GTK resources): Fix various typos.

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

@c Indexing guidelines

@c I assume that all indexes will be combinded.
@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, New Symbols, Standard Hooks, Top
@unnumbered Index

@c Print the indices

@printindex fn