Commit | Line | Data |
---|---|---|
94ec544d DL |
1 | @setfilename ../info/index |
2 | ||
3 | @c Indexing guidelines | |
4 | ||
5 | @c I assume that all indexes will be combinded. | |
6 | @c Therefore, if a generated findex and permutations | |
7 | @c cover the ways an index user would look up the entry, | |
8 | @c then no cindex is added. | |
9 | @c Concept index (cindex) entries will also be permuted. Therefore, they | |
10 | @c have no commas and few irrelevant connectives in them. | |
11 | ||
12 | @c I tried to include words in a cindex that give the context of the entry, | |
13 | @c particularly if there is more than one entry for the same concept. | |
14 | @c For example, "nil in keymap" | |
15 | @c Similarly for explicit findex and vindex entries, e.g., "print example". | |
16 | ||
17 | @c Error codes are given cindex entries, e.g., "end-of-file error". | |
18 | ||
19 | @c pindex is used for .el files and Unix programs | |
20 | ||
21 | @node Index, New Symbols, Standard Hooks, Top | |
22 | @unnumbered Index | |
23 | ||
24 | ||
25 | All variables, functions, keys, programs, files, and concepts are | |
26 | in this one index. | |
27 | ||
28 | All names and concepts are permuted, so they appear several times, one | |
29 | for each permutation of the parts of the name. For example, | |
30 | @code{function-name} would appear as @b{function-name} and @b{name, | |
31 | function-}. | |
32 | ||
33 | ||
34 | @c Print the indices | |
35 | ||
36 | @printindex fn | |
37 | ||
38 |