view man/lispref/index.texi @ 5296:d185fa593d5f last-version-with-netinstall

Specify ERROR_ME_WARN explicitly in specifier_instance_from_inst_list(). src/ChangeLog 2010-10-25 Aidan Kehoe <kehoea@parhasard.net> * specifier.c (specifier_instance_from_inst_list): Call call_with_suspended_errors() with ERROR_ME_WARN, explicitly; avoids the problem Giacomo Boffi describes in http://mid.gmane.org/19617.52517.341117.388679@aiuole.stru.polimi.it , but the specifier instantiation bug that makes XEmacs fail for him is still visible.
author Aidan Kehoe <kehoea@parhasard.net>
date Mon, 25 Oct 2010 17:57:37 +0100
parents 576fb035e263
children
line wrap: on
line source

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

@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

@ignore
All variables, functions, keys, programs, files, and concepts are
in this one index.

All names and concepts are permuted, so they appear several times, one
for each permutation of the parts of the name.  For example,
@code{function-name} would appear as @b{function-name} and @b{name,
function-}.  Key entries are not permuted, however.
@end ignore

@c Print the indices

@printindex fn