view lispref/index.unperm @ 40285:2869c6ed16fc

(texinfo-environments, texinfo-environment-regexp): Hoisted. (texinfo-font-lock-keywords): Use `italic' and `bold' faces. Only highlight the menu name in menu items. Setup `@foo ... @end foo' as text clones. (texinfo-clone-environment): New function. (texinfo-mode): Simplify auto-fill-inhibit-regexp. (texinfo-insert-block): Simplify. (texinfo-insert-quote): Insert a plain " if preceded by \ or if the command is repeated. (texinfo-last-unended-begin, texinfo-next-unmatched-end): New funs. (texinfo-insert-@end): Simplify.

@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