Mercurial > hg > xemacs-beta
view man/lispref/index.texi @ 4715:a357478dd457
Fix some test failures, mule-tests.el.
2009-10-12 Aidan Kehoe <kehoea@parhasard.net>
* automated/mule-tests.el :
Revert to the old Unicode mapping for scaron once we're finished
testing it.
Don't check the fixed-width coding systems with odd line endings
for ASCII-transparency; maybe we should, but that would require
that invalid sequence characters for on-disk ?\x0a be generated by
Macintosh line-ending coding systems, for example.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Mon, 12 Oct 2009 17:01:15 +0100 |
parents | 576fb035e263 |
children |
line wrap: on
line source
@c -*-texinfo-*- @setfilename ../../info/index.info @c Indexing guidelines @c I assume that all indexes will be combined. @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, , Standard Hooks, Top @unnumbered Index @ignore 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. @end ignore @c Print the indices @printindex fn