view lispref/index.texi @ 71366:1a62b8cd2100

(next_overlay_string): Fix assert. (push_it, pop_it): Handle composition and stretch specific values. Only handle it->slice in image (for now). (back_to_previous_visible_line_start): Continue search if newline is part of a compisition. Simplify. (reseat_1): Set it->object to buffer. (set_iterator_to_next): Set it->object to string or buffer, when setting it->method to GET_FROM_STRING or GET_FROM_BUFFER. (next_element_from_composition): Set it->object to buffer if not from string. (set_cursor_from_row): Only save start of string if not already done to handle multiple strings in a row.

@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