Mercurial > emacs
view lispref/index.perm @ 27889:51d0b4b8fc6a
(w32_display_info_for_display): Remove unused function.
(w32_draw_bitmap): Use pre-built bitmaps.
(w32_initialize_display_info): New function to initialize parts of
display info that are common to both GUI and console frames.
(w32_term_init): Use w32_initialize_display_info. Do not set
Vw32_num_mouse_buttons here, as it is not called for console
frames. Build bitmaps for indicating truncated lines etc.
(x_delete_display): Destroy pre-built bitmaps.
author | Jason Rumney <jasonr@gnu.org> |
---|---|
date | Sun, 27 Feb 2000 21:26:58 +0000 |
parents | 3fdcd0afea4b |
children | 23a1cea22d13 |
line wrap: on
line source
@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