Mercurial > emacs
view lispref/index.perm @ 29512:e222720769a0
(XTread_socket) <FocusIn>: Queue a FOCUS_IN_EVENT which
will be translated to a switch-frame event in when reading the
event queue. This is necessary because Emacs otherwise won't
perform a switch-frame to a new frame until some other event, for
example a keystroke event, forces it to do so. This has various
effects, one visible being that the cursor of a frame created with
C-x 5 2 or switched to with a window manager key binding like
A-TAB stays hollow because selected_window isn't on the newly
focused frame until the switch-frame is performed.
author | Gerd Moellmann <gerd@gnu.org> |
---|---|
date | Thu, 08 Jun 2000 20:56:24 +0000 |
parents | 3fdcd0afea4b |
children | 23a1cea22d13 |
line wrap: on
line source
@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 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-}. @c Print the indices @printindex fn