view lispref/index.unperm @ 45279:220c13a65624

(keymap_parent): New fun, extracted from Fkeymap_parent. (Fkeymap_parent, keymap_memberp, fix_submap_inheritance): Use it. (Fset_keymap_parent): Gcpro a bit more. (access_keymap): Gcpro around meta_map call and around the main loop. (get_keyelt): Gcpro when following indirect references. (copy_keymap_item): New fun, extracted from Fcopy_keymap. (copy_keymap_1, Fcopy_keymap): Use it. Don't copy the parent map. (Fdefine_key, Flookup_key): Gcpro before calling get_keymap. Remove useless ad-hoc remap code.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Tue, 14 May 2002 03:04:24 +0000
parents 3fdcd0afea4b
children
line wrap: on
line source

@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