Mercurial > hg > xemacs-beta
annotate man/lispref/index.texi @ 5096:e0587c615e8b
Updates to internals.texi
-------------------- ChangeLog entries follow: --------------------
man/ChangeLog addition:
2010-03-04 Ben Wing <ben@xemacs.org>
* internals/internals.texi (Top):
* internals/internals.texi (list-to-texinfo): Removed.
* internals/internals.texi (convert-list-to-texinfo): New.
* internals/internals.texi (table-to-texinfo): Removed.
* internals/internals.texi (convert-table-to-texinfo): New.
Update Lisp functions at top to newest versions.
* internals/internals.texi (A History of Emacs):
* internals/internals.texi (Through Version 18):
* internals/internals.texi (Lucid Emacs):
* internals/internals.texi (XEmacs):
* internals/internals.texi (The XEmacs Split):
* internals/internals.texi (Modules for Other Aspects of the Lisp Interpreter and Object System):
* internals/internals.texi (Introduction to Writing C Code):
* internals/internals.texi (Writing Good Comments):
* internals/internals.texi (Writing Macros):
* internals/internals.texi (Major Textual Changes):
* internals/internals.texi (Great Integral Type Renaming):
* internals/internals.texi (How to Regression-Test):
* internals/internals.texi (Creating a Branch):
* internals/internals.texi (Dynamic Arrays):
* internals/internals.texi (Allocation by Blocks):
* internals/internals.texi (mark_object):
* internals/internals.texi (gc_sweep):
* internals/internals.texi (Byte-Char Position Conversion):
* internals/internals.texi (Searching and Matching):
* internals/internals.texi (Introduction to Multilingual Issues #3):
* internals/internals.texi (Byte Types):
* internals/internals.texi (Different Ways of Seeing Internal Text):
* internals/internals.texi (Buffer Positions):
* internals/internals.texi (Basic internal-format APIs):
* internals/internals.texi (The DFC API):
* internals/internals.texi (General Guidelines for Writing Mule-Aware Code):
* internals/internals.texi (Mule-izing Code):
* internals/internals.texi (Locales):
* internals/internals.texi (More about code pages):
* internals/internals.texi (More about locales):
* internals/internals.texi (Unicode support under Windows):
* internals/internals.texi (The Frame):
* internals/internals.texi (The Non-Client Area):
* internals/internals.texi (The Client Area):
* internals/internals.texi (The Paned Area):
* internals/internals.texi (Text Areas):
* internals/internals.texi (The Displayable Area):
* internals/internals.texi (Event Queues):
* internals/internals.texi (Event Stream Callback Routines):
* internals/internals.texi (Focus Handling):
* internals/internals.texi (Future Work -- Autodetection):
Replace " with ``, '' (not complete, maybe about halfway through).
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Thu, 04 Mar 2010 07:19:03 -0600 |
| 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 |