From 94ec544dde013824d30184af6a20daedcc992fb2 Mon Sep 17 00:00:00 2001 From: Dave Love Date: Fri, 3 Dec 1999 18:20:46 +0000 Subject: *** empty log message *** --- lispref/index.perm | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 lispref/index.perm (limited to 'lispref/index.perm') diff --git a/lispref/index.perm b/lispref/index.perm new file mode 100644 index 00000000000..aeccc6b4a7f --- /dev/null +++ b/lispref/index.perm @@ -0,0 +1,38 @@ +@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 + + +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-}. + + +@c Print the indices + +@printindex fn + + -- cgit v1.2.1