view lispref/index.texi @ 60130:f513e6d34868

(check_it, init_from_display_pos, handle_stop) (setup_for_ellipsis, handle_single_display_spec) (handle_composition_prop, next_overlay_string) (get_overlay_strings, reseat_1, reseat_to_string) (next_element_from_ellipsis, BUFFER_POS_REACHED_P) (in_display_vector_p, display_line, get_next_display_element): Change it->method from function pointer to enum. (get_next_element): New array to map it->method to function. (get_next_display_element): Use it. (set_iterator_to_next): Use switch instead of if/else chain.
author Kim F. Storm <storm@cua.dk>
date Wed, 16 Feb 2005 23:45:03 +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