view doc/lispref/index.texi @ 101460:27ea311fecfa

2009-01-25 Carsten Dominik <[e-mail]> * org.texi (References): Add information about remote references. (Built-in table editor): Document `C-c RET' in tables. (Math symbols, Quoting LaTeX code): Mention that simple LaTeX macros survive LaTeX export. (Images in LaTeX export): Show how to create a reference to a figure. (Sectioning structure): Document that the LaTeX class can be specified in a property. (Text areas in HTML export): New section. (External links): Add examples for text search and ID links. (Built-in table editor): Remove the descriptio of `C-c C-q', it not longer works. (Literal examples): Document that a space must follow the colon in short examples. (Relative timer): Document `org-timer-stop'. (Footnotes): New section. (Footnote markup): Shorten section and refer to new Footnote section. (Literal examples): Add documentation for line numbering in and references to code examples. (CSS support): Fix the description of default CSS styles. (Capturing column view): Document "file:path/to/file.org" as an allowed value for the ID property of a dynamic block copying column view.

@c -*-texinfo-*-
@setfilename ../../info/index

@c Indexing guidelines

@c I assume that all indexes will be combined.
@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, , Standard Hooks, Top
@unnumbered Index

@c Print the indices

@printindex fn