view man/lispref/index.texi @ 2393:2d4dd2ef74e7

[xemacs-hg @ 2004-11-16 07:37:29 by ben] internals update internals/internals.texi: Add sections on Basic Types and Low-Level Allocation. Move module docs here. Incorporate dynamic array and blocktype docs from source. Add info on beta releases up to present. Redo chapter on "Rules When Writing New C Code", grouping stuff together properly. Put "Major Textual Changes" under this chapter. Incorporate etc/CODING-STANDARDS. Add discussion sections on "Instantiators and Generic Property Accessors" and "Switching to C++". Fill out discussion on garbage collection. Incorporate backtraces showing crashes due to problems with redisplay-critical-section protection.
author ben
date Tue, 16 Nov 2004 07:37:31 +0000
parents 576fb035e263
children
line wrap: on
line source

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

@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

@ignore
All variables, functions, keys, programs, files, and concepts are
in this one index.

All names and concepts are permuted, so they appear several times, one
for each permutation of the parts of the name.  For example,
@code{function-name} would appear as @b{function-name} and @b{name,
function-}.  Key entries are not permuted, however.
@end ignore

@c Print the indices

@printindex fn