DataMuseum.dk

top - metrics - download

    Length: 1275 (0x4fb)
    Types: TextFile
    Names: »index-unpermuted.texinfo«

└─⟦a05ed705a⟧ Bits:30007078 DKUUG GNU 2/12/89
    └─⟦c06c473ab⟧ »./UNRELEASED/lispref.tar.Z« 
        └─⟦1b57a2ffe⟧ 
            └─⟦this⟧ »index-unpermuted.texinfo« 

TextFile

@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.  (Therefore, this way of printing indices is not 
@c recommended.  The advantage is many fewer pages...)
@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
@iftex
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.

@c Print the indices

@printindex fn

@end iftex