Mercurial > hg > xemacs-beta
annotate man/lispref/index.texi @ 5361:62b9ef1ed4ac
Change "special form" to "special operator" in the manuals, too
2011-03-01 Aidan Kehoe <kehoea@parhasard.net>
* lispref/commands.texi (Using Interactive):
* lispref/compile.texi (Eval During Compile):
* lispref/compile.texi (Compiled-Function Objects):
* lispref/control.texi (Sequencing):
* lispref/control.texi (Conditionals):
* lispref/control.texi (Combining Conditions):
* lispref/control.texi (Iteration):
* lispref/control.texi (Catch and Throw):
* lispref/control.texi (Handling Errors):
* lispref/control.texi (Cleanups):
* lispref/display.texi (Temporary Displays):
* lispref/eval.texi (Quoting):
* lispref/eval.texi (Multiple values):
* lispref/frames.texi (Input Focus):
* lispref/functions.texi (Argument List):
* lispref/functions.texi (Defining Functions):
* lispref/functions.texi (Anonymous Functions):
* lispref/internationalization.texi (Level 3 Primitives):
* lispref/internationalization.texi (Domain Specification):
* lispref/intro.texi (A Sample Function Description):
* lispref/intro.texi (A Sample Variable Description):
* lispref/lists.texi (Sets And Lists):
* lispref/macros.texi (Defining Macros):
* lispref/macros.texi (Backquote):
* lispref/positions.texi (Excursions):
* lispref/positions.texi (Narrowing):
* lispref/searching.texi (Saving Match Data):
* lispref/sequences.texi (Sequence Functions):
* lispref/sequences.texi (Array Functions):
* lispref/specifiers.texi (Adding Specifications):
* lispref/variables.texi (Local Variables):
* lispref/variables.texi (Defining Variables):
* lispref/variables.texi (Setting Variables):
* lispref/variables.texi (Default Value):
* lispref/windows.texi (Selecting Windows):
* lispref/windows.texi (Window Configurations):
No longer use @defspec, since we no longer use the term "special
form"; instead use @deffn {Special Operator}. Unfortunately
there's no way in texinfo to redefine @defspec in one place.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Tue, 01 Mar 2011 14:18:45 +0000 |
| parents | 576fb035e263 |
| children |
| rev | line source |
|---|---|
| 398 | 1 @c -*-texinfo-*- |
| 2 @setfilename ../../info/index.info | |
| 3 | |
| 4 @c Indexing guidelines | |
| 5 | |
| 6 @c I assume that all indexes will be combined. | |
| 7 @c Therefore, if a generated findex and permutations | |
| 8 @c cover the ways an index user would look up the entry, | |
| 9 @c then no cindex is added. | |
| 10 @c Concept index (cindex) entries will also be permuted. Therefore, they | |
| 11 @c have no commas and few irrelevant connectives in them. | |
| 12 | |
| 13 @c I tried to include words in a cindex that give the context of the entry, | |
| 14 @c particularly if there is more than one entry for the same concept. | |
| 15 @c For example, "nil in keymap" | |
| 16 @c Similarly for explicit findex and vindex entries, e.g. "print example". | |
| 17 | |
| 18 @c Error codes are given cindex entries, e.g. "end-of-file error". | |
| 19 | |
| 20 @c pindex is used for .el files and Unix programs | |
| 21 | |
| 22 @node Index, , Standard Hooks, Top | |
| 23 @unnumbered Index | |
| 24 | |
| 25 @ignore | |
| 26 All variables, functions, keys, programs, files, and concepts are | |
| 444 | 27 in this one index. |
| 398 | 28 |
| 29 All names and concepts are permuted, so they appear several times, one | |
| 30 for each permutation of the parts of the name. For example, | |
| 31 @code{function-name} would appear as @b{function-name} and @b{name, | |
| 32 function-}. Key entries are not permuted, however. | |
| 33 @end ignore | |
| 34 | |
| 35 @c Print the indices | |
| 36 | |
| 37 @printindex fn |