Mercurial > emacs
view lispref/index.texi @ 69055:43656cd3b1ab
(NEW FEATURES): Completed work on this item:
Rework how fringe bitmaps are defined and used.
Currently, bitmap usage and bitmap appearence are "mixed-up" in a
one-level representation. It would be cleaner to split the
representation into a two-level model where first level maps
bitmap usage to a bitmap name, and second level maps bitmap name to
a bitmap appearence.
author | Kim F. Storm <storm@cua.dk> |
---|---|
date | Mon, 20 Feb 2006 22:24:10 +0000 |
parents | 26a5da04740c |
children | 7a84d4874322 |
line wrap: on
line source
@c -*-texinfo-*- @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 @c Print the indices @printindex fn