view man/lispref/index.texi @ 5858:36934833b4f3

#'event-matches-key-specifier-p, check keysyms and modifiers too on TTY src/ChangeLog addition: 2015-03-14 Aidan Kehoe <kehoea@parhasard.net> * keymap.c (event_matches_key_specifier_p): If on a TTY, check the keysym and modifiers too, before converting both events to characters and comparing them. We may well have seen a function key (by means of function-key-map) and it is actively unhelpful for (event-matches-key-specifier-p (character-to-event 'f1) 'f1) to given nil when the current device is a TTY.
author Aidan Kehoe <kehoea@parhasard.net>
date Sat, 14 Mar 2015 00:07:50 +0000
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