view lispref/index.texi @ 54700:677905e471e2

(font-lock): Don't require any more. (compilation-error-properties, compilation-start, compilation-sentinel) (compilation-filter, next-error): Use with-current-buffer. (compilation-skip-to-next-location, compilation-skip-threshold) (compilation-skip-visited): Move to silence the byte-compiler. (compilation-setup): Simplify. (compilation-next-error): Use line-(beginning|end)-position. Make sure `pt' is non-nil before using compilation-loop. (compile-goto-error): Add optional event arg. Use it. (compile-mouse-goto-error): Make it an alias of compile-goto-error. (compilation-minor-mode-map, compilation-shell-minor-mode-map): Update the binding for mouse-2. (first-error): Set compilation-current-error to nil rather than bob. (compilation-parsing-end, compilation-parse-errors-function) (compilation-error-list, compilation-old-error-list): "New" compatibility variables. (compile-buffer-substring, compilation-compat-error-properties) (compilation-compat-parse-errors, compilation-forget-errors): New compatibility functions. (compilation-mode-font-lock-keywords): Use them.

@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