[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/index.perm [lexbind]
From: |
Miles Bader |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/index.perm [lexbind] |
Date: |
Thu, 20 Nov 2003 19:36:46 -0500 |
Index: emacs/lispref/index.perm
diff -c emacs/lispref/index.perm:1.1.18.1 emacs/lispref/index.perm:removed
*** emacs/lispref/index.perm:1.1.18.1 Fri Apr 4 01:20:41 2003
--- emacs/lispref/index.perm Thu Nov 20 19:36:46 2003
***************
*** 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
-
-
--- 0 ----
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/lispref/index.perm [lexbind],
Miles Bader <=