Mercurial > emacs
annotate doc/lispref/commands.texi @ 99007:847cf809659f
*** empty log message ***
author | Alan Mackenzie <acm@muc.de> |
---|---|
date | Tue, 21 Oct 2008 21:12:33 +0000 |
parents | fa98223dc5ff |
children | 0ee463f8cc63 |
rev | line source |
---|---|
84053 | 1 @c -*-texinfo-*- |
2 @c This is part of the GNU Emacs Lisp Reference Manual. | |
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2001, 2002, | |
87649 | 4 @c 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. |
84053 | 5 @c See the file elisp.texi for copying conditions. |
84116
0ba80d073e27
(setfilename): Go up one more level to ../../info.
Glenn Morris <rgm@gnu.org>
parents:
84053
diff
changeset
|
6 @setfilename ../../info/commands |
84053 | 7 @node Command Loop, Keymaps, Minibuffers, Top |
8 @chapter Command Loop | |
9 @cindex editor command loop | |
10 @cindex command loop | |
11 | |
12 When you run Emacs, it enters the @dfn{editor command loop} almost | |
13 immediately. This loop reads key sequences, executes their definitions, | |
14 and displays the results. In this chapter, we describe how these things | |
15 are done, and the subroutines that allow Lisp programs to do them. | |
16 | |
17 @menu | |
18 * Command Overview:: How the command loop reads commands. | |
19 * Defining Commands:: Specifying how a function should read arguments. | |
20 * Interactive Call:: Calling a command, so that it will read arguments. | |
85311 | 21 * Distinguish Interactive:: Making a command distinguish interactive calls. |
84053 | 22 * Command Loop Info:: Variables set by the command loop for you to examine. |
23 * Adjusting Point:: Adjustment of point after a command. | |
24 * Input Events:: What input looks like when you read it. | |
25 * Reading Input:: How to read input events from the keyboard or mouse. | |
26 * Special Events:: Events processed immediately and individually. | |
27 * Waiting:: Waiting for user input or elapsed time. | |
28 * Quitting:: How @kbd{C-g} works. How to catch or defer quitting. | |
29 * Prefix Command Arguments:: How the commands to set prefix args work. | |
30 * Recursive Editing:: Entering a recursive edit, | |
31 and why you usually shouldn't. | |
32 * Disabling Commands:: How the command loop handles disabled commands. | |
33 * Command History:: How the command history is set up, and how accessed. | |
34 * Keyboard Macros:: How keyboard macros are implemented. | |
35 @end menu | |
36 | |
37 @node Command Overview | |
38 @section Command Loop Overview | |
39 | |
40 The first thing the command loop must do is read a key sequence, which | |
41 is a sequence of events that translates into a command. It does this by | |
42 calling the function @code{read-key-sequence}. Your Lisp code can also | |
43 call this function (@pxref{Key Sequence Input}). Lisp programs can also | |
44 do input at a lower level with @code{read-event} (@pxref{Reading One | |
45 Event}) or discard pending input with @code{discard-input} | |
46 (@pxref{Event Input Misc}). | |
47 | |
48 The key sequence is translated into a command through the currently | |
49 active keymaps. @xref{Key Lookup}, for information on how this is done. | |
50 The result should be a keyboard macro or an interactively callable | |
51 function. If the key is @kbd{M-x}, then it reads the name of another | |
52 command, which it then calls. This is done by the command | |
53 @code{execute-extended-command} (@pxref{Interactive Call}). | |
54 | |
55 To execute a command requires first reading the arguments for it. | |
56 This is done by calling @code{command-execute} (@pxref{Interactive | |
57 Call}). For commands written in Lisp, the @code{interactive} | |
58 specification says how to read the arguments. This may use the prefix | |
59 argument (@pxref{Prefix Command Arguments}) or may read with prompting | |
60 in the minibuffer (@pxref{Minibuffers}). For example, the command | |
61 @code{find-file} has an @code{interactive} specification which says to | |
62 read a file name using the minibuffer. The command's function body does | |
63 not use the minibuffer; if you call this command from Lisp code as a | |
64 function, you must supply the file name string as an ordinary Lisp | |
65 function argument. | |
66 | |
67 If the command is a string or vector (i.e., a keyboard macro) then | |
68 @code{execute-kbd-macro} is used to execute it. You can call this | |
69 function yourself (@pxref{Keyboard Macros}). | |
70 | |
71 To terminate the execution of a running command, type @kbd{C-g}. This | |
72 character causes @dfn{quitting} (@pxref{Quitting}). | |
73 | |
74 @defvar pre-command-hook | |
75 The editor command loop runs this normal hook before each command. At | |
76 that time, @code{this-command} contains the command that is about to | |
77 run, and @code{last-command} describes the previous command. | |
78 @xref{Command Loop Info}. | |
79 @end defvar | |
80 | |
81 @defvar post-command-hook | |
82 The editor command loop runs this normal hook after each command | |
83 (including commands terminated prematurely by quitting or by errors), | |
84 and also when the command loop is first entered. At that time, | |
85 @code{this-command} refers to the command that just ran, and | |
86 @code{last-command} refers to the command before that. | |
87 @end defvar | |
88 | |
89 Quitting is suppressed while running @code{pre-command-hook} and | |
90 @code{post-command-hook}. If an error happens while executing one of | |
91 these hooks, it terminates execution of the hook, and clears the hook | |
92 variable to @code{nil} so as to prevent an infinite loop of errors. | |
93 | |
94 A request coming into the Emacs server (@pxref{Emacs Server,,, | |
95 emacs, The GNU Emacs Manual}) runs these two hooks just as a keyboard | |
96 command does. | |
97 | |
98 @node Defining Commands | |
99 @section Defining Commands | |
100 @cindex defining commands | |
101 @cindex commands, defining | |
102 @cindex functions, making them interactive | |
103 @cindex interactive function | |
104 | |
105 A Lisp function becomes a command when its body contains, at top | |
98764
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
106 level, a form that calls the special form @code{interactive}, or if |
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
107 the function's symbol has an @code{interactive-form} property. This |
84053 | 108 form does nothing when actually executed, but its presence serves as a |
109 flag to indicate that interactive calling is permitted. Its argument | |
110 controls the reading of arguments for an interactive call. | |
111 | |
112 @menu | |
113 * Using Interactive:: General rules for @code{interactive}. | |
114 * Interactive Codes:: The standard letter-codes for reading arguments | |
115 in various ways. | |
116 * Interactive Examples:: Examples of how to read interactive arguments. | |
117 @end menu | |
118 | |
119 @node Using Interactive | |
120 @subsection Using @code{interactive} | |
121 @cindex arguments, interactive entry | |
122 | |
123 This section describes how to write the @code{interactive} form that | |
124 makes a Lisp function an interactively-callable command, and how to | |
125 examine a command's @code{interactive} form. | |
126 | |
127 @defspec interactive arg-descriptor | |
128 This special form declares that the function in which it appears is a | |
129 command, and that it may therefore be called interactively (via | |
130 @kbd{M-x} or by entering a key sequence bound to it). The argument | |
131 @var{arg-descriptor} declares how to compute the arguments to the | |
132 command when the command is called interactively. | |
133 | |
134 A command may be called from Lisp programs like any other function, but | |
135 then the caller supplies the arguments and @var{arg-descriptor} has no | |
136 effect. | |
137 | |
138 The @code{interactive} form has its effect because the command loop | |
139 (actually, its subroutine @code{call-interactively}) scans through the | |
140 function definition looking for it, before calling the function. Once | |
141 the function is called, all its body forms including the | |
142 @code{interactive} form are executed, but at this time | |
143 @code{interactive} simply returns @code{nil} without even evaluating its | |
144 argument. | |
98764
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
145 |
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
146 @cindex @code{interactive-form}, function property |
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
147 An interactive form can be added to a function post-facto via the |
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
148 @code{interactive-form} property of the function's symbol. |
fa98223dc5ff
(Defining Commands, Using Interactive): The interactive-form of a function
Eli Zaretskii <eliz@gnu.org>
parents:
98751
diff
changeset
|
149 @xref{Symbol Plists}. |
84053 | 150 @end defspec |
151 | |
152 There are three possibilities for the argument @var{arg-descriptor}: | |
153 | |
154 @itemize @bullet | |
155 @item | |
156 It may be omitted or @code{nil}; then the command is called with no | |
157 arguments. This leads quickly to an error if the command requires one | |
158 or more arguments. | |
159 | |
160 @item | |
161 It may be a string; then its contents should consist of a code character | |
162 followed by a prompt (which some code characters use and some ignore). | |
163 The prompt ends either with the end of the string or with a newline. | |
164 Here is a simple example: | |
165 | |
166 @smallexample | |
167 (interactive "bFrobnicate buffer: ") | |
168 @end smallexample | |
169 | |
170 @noindent | |
171 The code letter @samp{b} says to read the name of an existing buffer, | |
172 with completion. The buffer name is the sole argument passed to the | |
173 command. The rest of the string is a prompt. | |
174 | |
175 If there is a newline character in the string, it terminates the prompt. | |
176 If the string does not end there, then the rest of the string should | |
177 contain another code character and prompt, specifying another argument. | |
178 You can specify any number of arguments in this way. | |
179 | |
180 @c Emacs 19 feature | |
181 The prompt string can use @samp{%} to include previous argument values | |
182 (starting with the first argument) in the prompt. This is done using | |
183 @code{format} (@pxref{Formatting Strings}). For example, here is how | |
184 you could read the name of an existing buffer followed by a new name to | |
185 give to that buffer: | |
186 | |
187 @smallexample | |
188 @group | |
189 (interactive "bBuffer to rename: \nsRename buffer %s to: ") | |
190 @end group | |
191 @end smallexample | |
192 | |
193 @cindex @samp{*} in @code{interactive} | |
194 @cindex read-only buffers in interactive | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
195 If @samp{*} appears at the beginning of the string, then an error is |
84053 | 196 signaled if the buffer is read-only. |
197 | |
198 @cindex @samp{@@} in @code{interactive} | |
199 @c Emacs 19 feature | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
200 If @samp{@@} appears at the beginning of the string, and if the key |
84053 | 201 sequence used to invoke the command includes any mouse events, then |
202 the window associated with the first of those events is selected | |
203 before the command is run. | |
204 | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
205 @cindex @samp{^} in @code{interactive} |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
206 @cindex shift-selection, and @code{interactive} spec |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
207 If @samp{^} appears at the beginning of the string, and if the command |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
208 was invoked through @dfn{shift-translation}, set the mark and activate |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
209 the region temporarily, or extend an already active region, before the |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
210 command is run. If the command was invoked without shift-translation, |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
211 and the region is temporarily active, deactivate the region before the |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
212 command is run. Shift-translation is controlled on the user level by |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
213 @code{shift-select-mode}; see @ref{Shift Selection,,, emacs, The GNU |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
214 Emacs Manual}. |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
215 |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
216 You can use @samp{*}, @samp{@@}, and @code{^} together; the order does |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
217 not matter. Actual reading of arguments is controlled by the rest of |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
218 the prompt string (starting with the first character that is not |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
219 @samp{*}, @samp{@@}, or @samp{^}). |
84053 | 220 |
221 @item | |
222 It may be a Lisp expression that is not a string; then it should be a | |
223 form that is evaluated to get a list of arguments to pass to the | |
224 command. Usually this form will call various functions to read input | |
225 from the user, most often through the minibuffer (@pxref{Minibuffers}) | |
226 or directly from the keyboard (@pxref{Reading Input}). | |
227 | |
228 Providing point or the mark as an argument value is also common, but | |
229 if you do this @emph{and} read input (whether using the minibuffer or | |
230 not), be sure to get the integer values of point or the mark after | |
231 reading. The current buffer may be receiving subprocess output; if | |
232 subprocess output arrives while the command is waiting for input, it | |
233 could relocate point and the mark. | |
234 | |
235 Here's an example of what @emph{not} to do: | |
236 | |
237 @smallexample | |
238 (interactive | |
239 (list (region-beginning) (region-end) | |
240 (read-string "Foo: " nil 'my-history))) | |
241 @end smallexample | |
242 | |
243 @noindent | |
244 Here's how to avoid the problem, by examining point and the mark after | |
245 reading the keyboard input: | |
246 | |
247 @smallexample | |
248 (interactive | |
249 (let ((string (read-string "Foo: " nil 'my-history))) | |
250 (list (region-beginning) (region-end) string))) | |
251 @end smallexample | |
252 | |
253 @strong{Warning:} the argument values should not include any data | |
254 types that can't be printed and then read. Some facilities save | |
255 @code{command-history} in a file to be read in the subsequent | |
256 sessions; if a command's arguments contain a data type that prints | |
257 using @samp{#<@dots{}>} syntax, those facilities won't work. | |
258 | |
259 There are, however, a few exceptions: it is ok to use a limited set of | |
260 expressions such as @code{(point)}, @code{(mark)}, | |
261 @code{(region-beginning)}, and @code{(region-end)}, because Emacs | |
262 recognizes them specially and puts the expression (rather than its | |
263 value) into the command history. To see whether the expression you | |
264 wrote is one of these exceptions, run the command, then examine | |
265 @code{(car command-history)}. | |
266 @end itemize | |
267 | |
268 @cindex examining the @code{interactive} form | |
269 @defun interactive-form function | |
270 This function returns the @code{interactive} form of @var{function}. | |
271 If @var{function} is an interactively callable function | |
272 (@pxref{Interactive Call}), the value is the command's | |
273 @code{interactive} form @code{(interactive @var{spec})}, which | |
274 specifies how to compute its arguments. Otherwise, the value is | |
275 @code{nil}. If @var{function} is a symbol, its function definition is | |
276 used. | |
277 @end defun | |
278 | |
279 @node Interactive Codes | |
280 @comment node-name, next, previous, up | |
281 @subsection Code Characters for @code{interactive} | |
282 @cindex interactive code description | |
283 @cindex description for interactive codes | |
284 @cindex codes, interactive, description of | |
285 @cindex characters for interactive codes | |
286 | |
287 The code character descriptions below contain a number of key words, | |
288 defined here as follows: | |
289 | |
290 @table @b | |
291 @item Completion | |
292 @cindex interactive completion | |
293 Provide completion. @key{TAB}, @key{SPC}, and @key{RET} perform name | |
294 completion because the argument is read using @code{completing-read} | |
295 (@pxref{Completion}). @kbd{?} displays a list of possible completions. | |
296 | |
297 @item Existing | |
298 Require the name of an existing object. An invalid name is not | |
299 accepted; the commands to exit the minibuffer do not exit if the current | |
300 input is not valid. | |
301 | |
302 @item Default | |
303 @cindex default argument string | |
304 A default value of some sort is used if the user enters no text in the | |
305 minibuffer. The default depends on the code character. | |
306 | |
307 @item No I/O | |
308 This code letter computes an argument without reading any input. | |
309 Therefore, it does not use a prompt string, and any prompt string you | |
310 supply is ignored. | |
311 | |
312 Even though the code letter doesn't use a prompt string, you must follow | |
313 it with a newline if it is not the last code character in the string. | |
314 | |
315 @item Prompt | |
316 A prompt immediately follows the code character. The prompt ends either | |
317 with the end of the string or with a newline. | |
318 | |
319 @item Special | |
320 This code character is meaningful only at the beginning of the | |
321 interactive string, and it does not look for a prompt or a newline. | |
322 It is a single, isolated character. | |
323 @end table | |
324 | |
325 @cindex reading interactive arguments | |
326 Here are the code character descriptions for use with @code{interactive}: | |
327 | |
328 @table @samp | |
329 @item * | |
330 Signal an error if the current buffer is read-only. Special. | |
331 | |
332 @item @@ | |
333 Select the window mentioned in the first mouse event in the key | |
334 sequence that invoked this command. Special. | |
335 | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
336 @item ^ |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
337 If the command was invoked through shift-translation, set the mark and |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
338 activate the region temporarily, or extend an already active region, |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
339 before the command is run. If the command was invoked without |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
340 shift-translation, and the region is temporarily active, deactivate |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
341 the region before the command is run. Special. |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
342 |
84053 | 343 @item a |
344 A function name (i.e., a symbol satisfying @code{fboundp}). Existing, | |
345 Completion, Prompt. | |
346 | |
347 @item b | |
348 The name of an existing buffer. By default, uses the name of the | |
349 current buffer (@pxref{Buffers}). Existing, Completion, Default, | |
350 Prompt. | |
351 | |
352 @item B | |
353 A buffer name. The buffer need not exist. By default, uses the name of | |
354 a recently used buffer other than the current buffer. Completion, | |
355 Default, Prompt. | |
356 | |
357 @item c | |
358 A character. The cursor does not move into the echo area. Prompt. | |
359 | |
360 @item C | |
361 A command name (i.e., a symbol satisfying @code{commandp}). Existing, | |
362 Completion, Prompt. | |
363 | |
364 @item d | |
365 @cindex position argument | |
366 The position of point, as an integer (@pxref{Point}). No I/O. | |
367 | |
368 @item D | |
369 A directory name. The default is the current default directory of the | |
370 current buffer, @code{default-directory} (@pxref{File Name Expansion}). | |
371 Existing, Completion, Default, Prompt. | |
372 | |
373 @item e | |
374 The first or next mouse event in the key sequence that invoked the command. | |
375 More precisely, @samp{e} gets events that are lists, so you can look at | |
376 the data in the lists. @xref{Input Events}. No I/O. | |
377 | |
378 You can use @samp{e} more than once in a single command's interactive | |
379 specification. If the key sequence that invoked the command has | |
380 @var{n} events that are lists, the @var{n}th @samp{e} provides the | |
381 @var{n}th such event. Events that are not lists, such as function keys | |
382 and @acronym{ASCII} characters, do not count where @samp{e} is concerned. | |
383 | |
384 @item f | |
385 A file name of an existing file (@pxref{File Names}). The default | |
386 directory is @code{default-directory}. Existing, Completion, Default, | |
387 Prompt. | |
388 | |
389 @item F | |
390 A file name. The file need not exist. Completion, Default, Prompt. | |
391 | |
392 @item G | |
393 A file name. The file need not exist. If the user enters just a | |
394 directory name, then the value is just that directory name, with no | |
395 file name within the directory added. Completion, Default, Prompt. | |
396 | |
397 @item i | |
398 An irrelevant argument. This code always supplies @code{nil} as | |
399 the argument's value. No I/O. | |
400 | |
401 @item k | |
402 A key sequence (@pxref{Key Sequences}). This keeps reading events | |
403 until a command (or undefined command) is found in the current key | |
404 maps. The key sequence argument is represented as a string or vector. | |
405 The cursor does not move into the echo area. Prompt. | |
406 | |
407 If @samp{k} reads a key sequence that ends with a down-event, it also | |
408 reads and discards the following up-event. You can get access to that | |
409 up-event with the @samp{U} code character. | |
410 | |
411 This kind of input is used by commands such as @code{describe-key} and | |
412 @code{global-set-key}. | |
413 | |
414 @item K | |
415 A key sequence, whose definition you intend to change. This works like | |
416 @samp{k}, except that it suppresses, for the last input event in the key | |
417 sequence, the conversions that are normally used (when necessary) to | |
418 convert an undefined key into a defined one. | |
419 | |
420 @item m | |
421 @cindex marker argument | |
422 The position of the mark, as an integer. No I/O. | |
423 | |
424 @item M | |
425 Arbitrary text, read in the minibuffer using the current buffer's input | |
426 method, and returned as a string (@pxref{Input Methods,,, emacs, The GNU | |
427 Emacs Manual}). Prompt. | |
428 | |
429 @item n | |
430 A number, read with the minibuffer. If the input is not a number, the | |
431 user has to try again. @samp{n} never uses the prefix argument. | |
432 Prompt. | |
433 | |
434 @item N | |
435 The numeric prefix argument; but if there is no prefix argument, read | |
436 a number as with @kbd{n}. The value is always a number. @xref{Prefix | |
437 Command Arguments}. Prompt. | |
438 | |
439 @item p | |
440 @cindex numeric prefix argument usage | |
441 The numeric prefix argument. (Note that this @samp{p} is lower case.) | |
442 No I/O. | |
443 | |
444 @item P | |
445 @cindex raw prefix argument usage | |
446 The raw prefix argument. (Note that this @samp{P} is upper case.) No | |
447 I/O. | |
448 | |
449 @item r | |
450 @cindex region argument | |
451 Point and the mark, as two numeric arguments, smallest first. This is | |
452 the only code letter that specifies two successive arguments rather than | |
453 one. No I/O. | |
454 | |
455 @item s | |
456 Arbitrary text, read in the minibuffer and returned as a string | |
457 (@pxref{Text from Minibuffer}). Terminate the input with either | |
458 @kbd{C-j} or @key{RET}. (@kbd{C-q} may be used to include either of | |
459 these characters in the input.) Prompt. | |
460 | |
461 @item S | |
462 An interned symbol whose name is read in the minibuffer. Any whitespace | |
463 character terminates the input. (Use @kbd{C-q} to include whitespace in | |
464 the string.) Other characters that normally terminate a symbol (e.g., | |
465 parentheses and brackets) do not do so here. Prompt. | |
466 | |
467 @item U | |
468 A key sequence or @code{nil}. Can be used after a @samp{k} or | |
469 @samp{K} argument to get the up-event that was discarded (if any) | |
470 after @samp{k} or @samp{K} read a down-event. If no up-event has been | |
471 discarded, @samp{U} provides @code{nil} as the argument. No I/O. | |
472 | |
473 @item v | |
474 A variable declared to be a user option (i.e., satisfying the | |
475 predicate @code{user-variable-p}). This reads the variable using | |
476 @code{read-variable}. @xref{Definition of read-variable}. Existing, | |
477 Completion, Prompt. | |
478 | |
479 @item x | |
480 A Lisp object, specified with its read syntax, terminated with a | |
481 @kbd{C-j} or @key{RET}. The object is not evaluated. @xref{Object from | |
482 Minibuffer}. Prompt. | |
483 | |
484 @item X | |
485 @cindex evaluated expression argument | |
486 A Lisp form's value. @samp{X} reads as @samp{x} does, then evaluates | |
487 the form so that its value becomes the argument for the command. | |
488 Prompt. | |
489 | |
490 @item z | |
491 A coding system name (a symbol). If the user enters null input, the | |
492 argument value is @code{nil}. @xref{Coding Systems}. Completion, | |
493 Existing, Prompt. | |
494 | |
495 @item Z | |
496 A coding system name (a symbol)---but only if this command has a prefix | |
497 argument. With no prefix argument, @samp{Z} provides @code{nil} as the | |
498 argument value. Completion, Existing, Prompt. | |
499 @end table | |
500 | |
501 @node Interactive Examples | |
502 @comment node-name, next, previous, up | |
503 @subsection Examples of Using @code{interactive} | |
504 @cindex examples of using @code{interactive} | |
505 @cindex @code{interactive}, examples of using | |
506 | |
507 Here are some examples of @code{interactive}: | |
508 | |
509 @example | |
510 @group | |
511 (defun foo1 () ; @r{@code{foo1} takes no arguments,} | |
512 (interactive) ; @r{just moves forward two words.} | |
513 (forward-word 2)) | |
514 @result{} foo1 | |
515 @end group | |
516 | |
517 @group | |
518 (defun foo2 (n) ; @r{@code{foo2} takes one argument,} | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
519 (interactive "^p") ; @r{which is the numeric prefix.} |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
520 ; @r{under @code{shift-select-mode},} |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
521 ; @r{will activate or extend region.} |
84053 | 522 (forward-word (* 2 n))) |
523 @result{} foo2 | |
524 @end group | |
525 | |
526 @group | |
527 (defun foo3 (n) ; @r{@code{foo3} takes one argument,} | |
528 (interactive "nCount:") ; @r{which is read with the Minibuffer.} | |
529 (forward-word (* 2 n))) | |
530 @result{} foo3 | |
531 @end group | |
532 | |
533 @group | |
534 (defun three-b (b1 b2 b3) | |
535 "Select three existing buffers. | |
536 Put them into three windows, selecting the last one." | |
537 @end group | |
538 (interactive "bBuffer1:\nbBuffer2:\nbBuffer3:") | |
539 (delete-other-windows) | |
540 (split-window (selected-window) 8) | |
541 (switch-to-buffer b1) | |
542 (other-window 1) | |
543 (split-window (selected-window) 8) | |
544 (switch-to-buffer b2) | |
545 (other-window 1) | |
546 (switch-to-buffer b3)) | |
547 @result{} three-b | |
548 @group | |
549 (three-b "*scratch*" "declarations.texi" "*mail*") | |
550 @result{} nil | |
551 @end group | |
552 @end example | |
553 | |
554 @node Interactive Call | |
555 @section Interactive Call | |
556 @cindex interactive call | |
557 | |
558 After the command loop has translated a key sequence into a command it | |
559 invokes that command using the function @code{command-execute}. If the | |
560 command is a function, @code{command-execute} calls | |
561 @code{call-interactively}, which reads the arguments and calls the | |
562 command. You can also call these functions yourself. | |
563 | |
564 @defun commandp object &optional for-call-interactively | |
565 Returns @code{t} if @var{object} is suitable for calling interactively; | |
566 that is, if @var{object} is a command. Otherwise, returns @code{nil}. | |
567 | |
568 The interactively callable objects include strings and vectors (treated | |
569 as keyboard macros), lambda expressions that contain a top-level call to | |
570 @code{interactive}, byte-code function objects made from such lambda | |
571 expressions, autoload objects that are declared as interactive | |
572 (non-@code{nil} fourth argument to @code{autoload}), and some of the | |
573 primitive functions. | |
574 | |
575 A symbol satisfies @code{commandp} if its function definition | |
576 satisfies @code{commandp}. Keys and keymaps are not commands. | |
577 Rather, they are used to look up commands (@pxref{Keymaps}). | |
578 | |
579 If @var{for-call-interactively} is non-@code{nil}, then | |
580 @code{commandp} returns @code{t} only for objects that | |
581 @code{call-interactively} could call---thus, not for keyboard macros. | |
582 | |
583 See @code{documentation} in @ref{Accessing Documentation}, for a | |
584 realistic example of using @code{commandp}. | |
585 @end defun | |
586 | |
587 @defun call-interactively command &optional record-flag keys | |
588 This function calls the interactively callable function @var{command}, | |
589 reading arguments according to its interactive calling specifications. | |
590 It returns whatever @var{command} returns. An error is signaled if | |
591 @var{command} is not a function or if it cannot be called | |
592 interactively (i.e., is not a command). Note that keyboard macros | |
593 (strings and vectors) are not accepted, even though they are | |
594 considered commands, because they are not functions. If @var{command} | |
595 is a symbol, then @code{call-interactively} uses its function definition. | |
596 | |
597 @cindex record command history | |
598 If @var{record-flag} is non-@code{nil}, then this command and its | |
599 arguments are unconditionally added to the list @code{command-history}. | |
600 Otherwise, the command is added only if it uses the minibuffer to read | |
601 an argument. @xref{Command History}. | |
602 | |
603 The argument @var{keys}, if given, should be a vector which specifies | |
604 the sequence of events to supply if the command inquires which events | |
605 were used to invoke it. If @var{keys} is omitted or @code{nil}, the | |
606 default is the return value of @code{this-command-keys-vector}. | |
607 @xref{Definition of this-command-keys-vector}. | |
608 @end defun | |
609 | |
610 @defun command-execute command &optional record-flag keys special | |
611 @cindex keyboard macro execution | |
612 This function executes @var{command}. The argument @var{command} must | |
613 satisfy the @code{commandp} predicate; i.e., it must be an interactively | |
614 callable function or a keyboard macro. | |
615 | |
616 A string or vector as @var{command} is executed with | |
617 @code{execute-kbd-macro}. A function is passed to | |
618 @code{call-interactively}, along with the optional @var{record-flag} | |
619 and @var{keys}. | |
620 | |
621 A symbol is handled by using its function definition in its place. A | |
622 symbol with an @code{autoload} definition counts as a command if it was | |
623 declared to stand for an interactively callable function. Such a | |
624 definition is handled by loading the specified library and then | |
625 rechecking the definition of the symbol. | |
626 | |
627 The argument @var{special}, if given, means to ignore the prefix | |
628 argument and not clear it. This is used for executing special events | |
629 (@pxref{Special Events}). | |
630 @end defun | |
631 | |
632 @deffn Command execute-extended-command prefix-argument | |
633 @cindex read command name | |
634 This function reads a command name from the minibuffer using | |
635 @code{completing-read} (@pxref{Completion}). Then it uses | |
636 @code{command-execute} to call the specified command. Whatever that | |
637 command returns becomes the value of @code{execute-extended-command}. | |
638 | |
639 @cindex execute with prefix argument | |
640 If the command asks for a prefix argument, it receives the value | |
641 @var{prefix-argument}. If @code{execute-extended-command} is called | |
642 interactively, the current raw prefix argument is used for | |
643 @var{prefix-argument}, and thus passed on to whatever command is run. | |
644 | |
645 @c !!! Should this be @kindex? | |
646 @cindex @kbd{M-x} | |
647 @code{execute-extended-command} is the normal definition of @kbd{M-x}, | |
648 so it uses the string @w{@samp{M-x }} as a prompt. (It would be better | |
649 to take the prompt from the events used to invoke | |
650 @code{execute-extended-command}, but that is painful to implement.) A | |
651 description of the value of the prefix argument, if any, also becomes | |
652 part of the prompt. | |
653 | |
654 @example | |
655 @group | |
656 (execute-extended-command 3) | |
657 ---------- Buffer: Minibuffer ---------- | |
658 3 M-x forward-word RET | |
659 ---------- Buffer: Minibuffer ---------- | |
660 @result{} t | |
661 @end group | |
662 @end example | |
663 @end deffn | |
664 | |
85311 | 665 @node Distinguish Interactive |
666 @section Distinguish Interactive Calls | |
667 | |
668 Sometimes a command should display additional visual feedback (such | |
669 as an informative message in the echo area) for interactive calls | |
670 only. There are three ways to do this. The recommended way to test | |
671 whether the function was called using @code{call-interactively} is to | |
672 give it an optional argument @code{print-message} and use the | |
673 @code{interactive} spec to make it non-@code{nil} in interactive | |
674 calls. Here's an example: | |
675 | |
676 @example | |
677 (defun foo (&optional print-message) | |
678 (interactive "p") | |
679 (when print-message | |
680 (message "foo"))) | |
681 @end example | |
682 | |
683 @noindent | |
684 We use @code{"p"} because the numeric prefix argument is never | |
685 @code{nil}. Defined in this way, the function does display the | |
686 message when called from a keyboard macro. | |
687 | |
688 The above method with the additional argument is usually best, | |
689 because it allows callers to say ``treat this call as interactive.'' | |
690 But you can also do the job in a simpler way by testing | |
691 @code{called-interactively-p}. | |
692 | |
693 @defun called-interactively-p | |
694 This function returns @code{t} when the calling function was called | |
695 using @code{call-interactively}. | |
84053 | 696 |
697 If the containing function was called by Lisp evaluation (or with | |
698 @code{apply} or @code{funcall}), then it was not called interactively. | |
699 @end defun | |
700 | |
85311 | 701 Here's an example of using @code{called-interactively-p}: |
84053 | 702 |
703 @example | |
704 @group | |
705 (defun foo () | |
706 (interactive) | |
85311 | 707 (when (called-interactively-p) |
708 (message "foo")) | |
709 'haha) | |
84053 | 710 @result{} foo |
711 @end group | |
712 | |
713 @group | |
714 ;; @r{Type @kbd{M-x foo}.} | |
715 @print{} foo | |
716 @end group | |
717 | |
718 @group | |
85311 | 719 (foo) |
720 @result{} haha | |
721 @end group | |
722 @end example | |
723 | |
724 Here is another example that contrasts direct and indirect | |
725 calls to @code{called-interactively-p}. | |
726 | |
727 @example | |
728 @group | |
729 (defun bar () | |
730 (interactive) | |
731 (setq foobar (list (foo) (called-interactively-p)))) | |
732 @result{} bar | |
733 @end group | |
734 | |
735 @group | |
84053 | 736 ;; @r{Type @kbd{M-x bar}.} |
737 ;; @r{This does not display a message.} | |
738 @end group | |
739 | |
740 @group | |
741 foobar | |
742 @result{} (nil t) | |
743 @end group | |
744 @end example | |
745 | |
85311 | 746 If you want to treat commands run in keyboard macros just like calls |
747 from Lisp programs, test @code{interactive-p} instead of | |
748 @code{called-interactively-p}. | |
749 | |
750 @defun interactive-p | |
751 This function returns @code{t} if the containing function (the one | |
752 whose code includes the call to @code{interactive-p}) was called in | |
753 direct response to user input. This means that it was called with the | |
754 function @code{call-interactively}, and that a keyboard macro is | |
755 not running, and that Emacs is not running in batch mode. | |
84053 | 756 @end defun |
757 | |
758 @node Command Loop Info | |
759 @comment node-name, next, previous, up | |
760 @section Information from the Command Loop | |
761 | |
762 The editor command loop sets several Lisp variables to keep status | |
85114 | 763 records for itself and for commands that are run. With the exception of |
764 @code{this-command} and @code{last-command} it's generally a bad idea to | |
765 change any of these variables in a Lisp program. | |
84053 | 766 |
767 @defvar last-command | |
768 This variable records the name of the previous command executed by the | |
769 command loop (the one before the current command). Normally the value | |
770 is a symbol with a function definition, but this is not guaranteed. | |
771 | |
772 The value is copied from @code{this-command} when a command returns to | |
773 the command loop, except when the command has specified a prefix | |
774 argument for the following command. | |
775 | |
776 This variable is always local to the current terminal and cannot be | |
777 buffer-local. @xref{Multiple Displays}. | |
778 @end defvar | |
779 | |
780 @defvar real-last-command | |
781 This variable is set up by Emacs just like @code{last-command}, | |
782 but never altered by Lisp programs. | |
783 @end defvar | |
784 | |
85114 | 785 @defvar last-repeatable-command |
786 This variable stores the most recently executed command that was not | |
787 part of an input event. This is the command @code{repeat} will try to | |
788 repeat, @xref{Repeating,,, emacs, The GNU Emacs Manual}. | |
789 @end defvar | |
790 | |
84053 | 791 @defvar this-command |
792 @cindex current command | |
793 This variable records the name of the command now being executed by | |
794 the editor command loop. Like @code{last-command}, it is normally a symbol | |
795 with a function definition. | |
796 | |
797 The command loop sets this variable just before running a command, and | |
798 copies its value into @code{last-command} when the command finishes | |
799 (unless the command specified a prefix argument for the following | |
800 command). | |
801 | |
802 @cindex kill command repetition | |
803 Some commands set this variable during their execution, as a flag for | |
804 whatever command runs next. In particular, the functions for killing text | |
805 set @code{this-command} to @code{kill-region} so that any kill commands | |
806 immediately following will know to append the killed text to the | |
807 previous kill. | |
808 @end defvar | |
809 | |
810 If you do not want a particular command to be recognized as the previous | |
811 command in the case where it got an error, you must code that command to | |
812 prevent this. One way is to set @code{this-command} to @code{t} at the | |
813 beginning of the command, and set @code{this-command} back to its proper | |
814 value at the end, like this: | |
815 | |
816 @example | |
817 (defun foo (args@dots{}) | |
818 (interactive @dots{}) | |
819 (let ((old-this-command this-command)) | |
820 (setq this-command t) | |
821 @r{@dots{}do the work@dots{}} | |
822 (setq this-command old-this-command))) | |
823 @end example | |
824 | |
825 @noindent | |
826 We do not bind @code{this-command} with @code{let} because that would | |
827 restore the old value in case of error---a feature of @code{let} which | |
828 in this case does precisely what we want to avoid. | |
829 | |
830 @defvar this-original-command | |
831 This has the same value as @code{this-command} except when command | |
832 remapping occurs (@pxref{Remapping Commands}). In that case, | |
833 @code{this-command} gives the command actually run (the result of | |
834 remapping), and @code{this-original-command} gives the command that | |
835 was specified to run but remapped into another command. | |
836 @end defvar | |
837 | |
838 @defun this-command-keys | |
839 This function returns a string or vector containing the key sequence | |
840 that invoked the present command, plus any previous commands that | |
841 generated the prefix argument for this command. Any events read by the | |
842 command using @code{read-event} without a timeout get tacked on to the end. | |
843 | |
844 However, if the command has called @code{read-key-sequence}, it | |
845 returns the last read key sequence. @xref{Key Sequence Input}. The | |
846 value is a string if all events in the sequence were characters that | |
847 fit in a string. @xref{Input Events}. | |
848 | |
849 @example | |
850 @group | |
851 (this-command-keys) | |
852 ;; @r{Now use @kbd{C-u C-x C-e} to evaluate that.} | |
853 @result{} "^U^X^E" | |
854 @end group | |
855 @end example | |
856 @end defun | |
857 | |
858 @defun this-command-keys-vector | |
859 @anchor{Definition of this-command-keys-vector} | |
860 Like @code{this-command-keys}, except that it always returns the events | |
861 in a vector, so you don't need to deal with the complexities of storing | |
862 input events in a string (@pxref{Strings of Events}). | |
863 @end defun | |
864 | |
865 @defun clear-this-command-keys &optional keep-record | |
866 This function empties out the table of events for | |
867 @code{this-command-keys} to return. Unless @var{keep-record} is | |
868 non-@code{nil}, it also empties the records that the function | |
869 @code{recent-keys} (@pxref{Recording Input}) will subsequently return. | |
870 This is useful after reading a password, to prevent the password from | |
871 echoing inadvertently as part of the next command in certain cases. | |
872 @end defun | |
873 | |
874 @defvar last-nonmenu-event | |
875 This variable holds the last input event read as part of a key sequence, | |
876 not counting events resulting from mouse menus. | |
877 | |
878 One use of this variable is for telling @code{x-popup-menu} where to pop | |
879 up a menu. It is also used internally by @code{y-or-n-p} | |
880 (@pxref{Yes-or-No Queries}). | |
881 @end defvar | |
882 | |
883 @defvar last-command-event | |
884 @defvarx last-command-char | |
885 This variable is set to the last input event that was read by the | |
886 command loop as part of a command. The principal use of this variable | |
887 is in @code{self-insert-command}, which uses it to decide which | |
888 character to insert. | |
889 | |
890 @example | |
891 @group | |
892 last-command-event | |
893 ;; @r{Now use @kbd{C-u C-x C-e} to evaluate that.} | |
894 @result{} 5 | |
895 @end group | |
896 @end example | |
897 | |
898 @noindent | |
899 The value is 5 because that is the @acronym{ASCII} code for @kbd{C-e}. | |
900 | |
901 The alias @code{last-command-char} exists for compatibility with | |
902 Emacs version 18. | |
903 @end defvar | |
904 | |
905 @c Emacs 19 feature | |
906 @defvar last-event-frame | |
907 This variable records which frame the last input event was directed to. | |
908 Usually this is the frame that was selected when the event was | |
909 generated, but if that frame has redirected input focus to another | |
910 frame, the value is the frame to which the event was redirected. | |
911 @xref{Input Focus}. | |
912 | |
913 If the last event came from a keyboard macro, the value is @code{macro}. | |
914 @end defvar | |
915 | |
916 @node Adjusting Point | |
917 @section Adjusting Point After Commands | |
918 @cindex adjusting point | |
919 @cindex invisible/intangible text, and point | |
920 @cindex @code{display} property, and point display | |
921 @cindex @code{composition} property, and point display | |
922 | |
923 It is not easy to display a value of point in the middle of a | |
924 sequence of text that has the @code{display}, @code{composition} or | |
925 @code{intangible} property, or is invisible. Therefore, after a | |
926 command finishes and returns to the command loop, if point is within | |
927 such a sequence, the command loop normally moves point to the edge of | |
928 the sequence. | |
929 | |
930 A command can inhibit this feature by setting the variable | |
931 @code{disable-point-adjustment}: | |
932 | |
933 @defvar disable-point-adjustment | |
934 If this variable is non-@code{nil} when a command returns to the | |
935 command loop, then the command loop does not check for those text | |
936 properties, and does not move point out of sequences that have them. | |
937 | |
938 The command loop sets this variable to @code{nil} before each command, | |
939 so if a command sets it, the effect applies only to that command. | |
940 @end defvar | |
941 | |
942 @defvar global-disable-point-adjustment | |
943 If you set this variable to a non-@code{nil} value, the feature of | |
944 moving point out of these sequences is completely turned off. | |
945 @end defvar | |
946 | |
947 @node Input Events | |
948 @section Input Events | |
949 @cindex events | |
950 @cindex input events | |
951 | |
952 The Emacs command loop reads a sequence of @dfn{input events} that | |
953 represent keyboard or mouse activity. The events for keyboard activity | |
954 are characters or symbols; mouse events are always lists. This section | |
955 describes the representation and meaning of input events in detail. | |
956 | |
957 @defun eventp object | |
958 This function returns non-@code{nil} if @var{object} is an input event | |
959 or event type. | |
960 | |
961 Note that any symbol might be used as an event or an event type. | |
962 @code{eventp} cannot distinguish whether a symbol is intended by Lisp | |
963 code to be used as an event. Instead, it distinguishes whether the | |
964 symbol has actually been used in an event that has been read as input in | |
965 the current Emacs session. If a symbol has not yet been so used, | |
966 @code{eventp} returns @code{nil}. | |
967 @end defun | |
968 | |
969 @menu | |
970 * Keyboard Events:: Ordinary characters--keys with symbols on them. | |
971 * Function Keys:: Function keys--keys with names, not symbols. | |
972 * Mouse Events:: Overview of mouse events. | |
973 * Click Events:: Pushing and releasing a mouse button. | |
974 * Drag Events:: Moving the mouse before releasing the button. | |
975 * Button-Down Events:: A button was pushed and not yet released. | |
976 * Repeat Events:: Double and triple click (or drag, or down). | |
977 * Motion Events:: Just moving the mouse, not pushing a button. | |
978 * Focus Events:: Moving the mouse between frames. | |
979 * Misc Events:: Other events the system can generate. | |
980 * Event Examples:: Examples of the lists for mouse events. | |
981 * Classifying Events:: Finding the modifier keys in an event symbol. | |
982 Event types. | |
87519
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
983 * Accessing Mouse:: Functions to extract info from mouse events. |
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
984 * Accessing Scroll:: Functions to get info from scroll bar events. |
84053 | 985 * Strings of Events:: Special considerations for putting |
986 keyboard character events in a string. | |
987 @end menu | |
988 | |
989 @node Keyboard Events | |
990 @subsection Keyboard Events | |
991 @cindex keyboard events | |
992 | |
993 There are two kinds of input you can get from the keyboard: ordinary | |
994 keys, and function keys. Ordinary keys correspond to characters; the | |
995 events they generate are represented in Lisp as characters. The event | |
996 type of a character event is the character itself (an integer); see | |
997 @ref{Classifying Events}. | |
998 | |
999 @cindex modifier bits (of input character) | |
1000 @cindex basic code (of input character) | |
1001 An input character event consists of a @dfn{basic code} between 0 and | |
1002 524287, plus any or all of these @dfn{modifier bits}: | |
1003 | |
1004 @table @asis | |
1005 @item meta | |
1006 The | |
1007 @tex | |
1008 @math{2^{27}} | |
1009 @end tex | |
1010 @ifnottex | |
1011 2**27 | |
1012 @end ifnottex | |
1013 bit in the character code indicates a character | |
1014 typed with the meta key held down. | |
1015 | |
1016 @item control | |
1017 The | |
1018 @tex | |
1019 @math{2^{26}} | |
1020 @end tex | |
1021 @ifnottex | |
1022 2**26 | |
1023 @end ifnottex | |
1024 bit in the character code indicates a non-@acronym{ASCII} | |
1025 control character. | |
1026 | |
1027 @sc{ascii} control characters such as @kbd{C-a} have special basic | |
1028 codes of their own, so Emacs needs no special bit to indicate them. | |
1029 Thus, the code for @kbd{C-a} is just 1. | |
1030 | |
1031 But if you type a control combination not in @acronym{ASCII}, such as | |
1032 @kbd{%} with the control key, the numeric value you get is the code | |
1033 for @kbd{%} plus | |
1034 @tex | |
1035 @math{2^{26}} | |
1036 @end tex | |
1037 @ifnottex | |
1038 2**26 | |
1039 @end ifnottex | |
1040 (assuming the terminal supports non-@acronym{ASCII} | |
1041 control characters). | |
1042 | |
1043 @item shift | |
1044 The | |
1045 @tex | |
1046 @math{2^{25}} | |
1047 @end tex | |
1048 @ifnottex | |
1049 2**25 | |
1050 @end ifnottex | |
1051 bit in the character code indicates an @acronym{ASCII} control | |
1052 character typed with the shift key held down. | |
1053 | |
1054 For letters, the basic code itself indicates upper versus lower case; | |
1055 for digits and punctuation, the shift key selects an entirely different | |
1056 character with a different basic code. In order to keep within the | |
1057 @acronym{ASCII} character set whenever possible, Emacs avoids using the | |
1058 @tex | |
1059 @math{2^{25}} | |
1060 @end tex | |
1061 @ifnottex | |
1062 2**25 | |
1063 @end ifnottex | |
1064 bit for those characters. | |
1065 | |
1066 However, @acronym{ASCII} provides no way to distinguish @kbd{C-A} from | |
1067 @kbd{C-a}, so Emacs uses the | |
1068 @tex | |
1069 @math{2^{25}} | |
1070 @end tex | |
1071 @ifnottex | |
1072 2**25 | |
1073 @end ifnottex | |
1074 bit in @kbd{C-A} and not in | |
1075 @kbd{C-a}. | |
1076 | |
1077 @item hyper | |
1078 The | |
1079 @tex | |
1080 @math{2^{24}} | |
1081 @end tex | |
1082 @ifnottex | |
1083 2**24 | |
1084 @end ifnottex | |
1085 bit in the character code indicates a character | |
1086 typed with the hyper key held down. | |
1087 | |
1088 @item super | |
1089 The | |
1090 @tex | |
1091 @math{2^{23}} | |
1092 @end tex | |
1093 @ifnottex | |
1094 2**23 | |
1095 @end ifnottex | |
1096 bit in the character code indicates a character | |
1097 typed with the super key held down. | |
1098 | |
1099 @item alt | |
1100 The | |
1101 @tex | |
1102 @math{2^{22}} | |
1103 @end tex | |
1104 @ifnottex | |
1105 2**22 | |
1106 @end ifnottex | |
1107 bit in the character code indicates a character typed with | |
1108 the alt key held down. (On some terminals, the key labeled @key{ALT} | |
1109 is actually the meta key.) | |
1110 @end table | |
1111 | |
1112 It is best to avoid mentioning specific bit numbers in your program. | |
1113 To test the modifier bits of a character, use the function | |
1114 @code{event-modifiers} (@pxref{Classifying Events}). When making key | |
1115 bindings, you can use the read syntax for characters with modifier bits | |
1116 (@samp{\C-}, @samp{\M-}, and so on). For making key bindings with | |
1117 @code{define-key}, you can use lists such as @code{(control hyper ?x)} to | |
1118 specify the characters (@pxref{Changing Key Bindings}). The function | |
1119 @code{event-convert-list} converts such a list into an event type | |
1120 (@pxref{Classifying Events}). | |
1121 | |
1122 @node Function Keys | |
1123 @subsection Function Keys | |
1124 | |
1125 @cindex function keys | |
1126 Most keyboards also have @dfn{function keys}---keys that have names or | |
1127 symbols that are not characters. Function keys are represented in Emacs | |
1128 Lisp as symbols; the symbol's name is the function key's label, in lower | |
1129 case. For example, pressing a key labeled @key{F1} places the symbol | |
1130 @code{f1} in the input stream. | |
1131 | |
1132 The event type of a function key event is the event symbol itself. | |
1133 @xref{Classifying Events}. | |
1134 | |
1135 Here are a few special cases in the symbol-naming convention for | |
1136 function keys: | |
1137 | |
1138 @table @asis | |
1139 @item @code{backspace}, @code{tab}, @code{newline}, @code{return}, @code{delete} | |
1140 These keys correspond to common @acronym{ASCII} control characters that have | |
1141 special keys on most keyboards. | |
1142 | |
1143 In @acronym{ASCII}, @kbd{C-i} and @key{TAB} are the same character. If the | |
1144 terminal can distinguish between them, Emacs conveys the distinction to | |
1145 Lisp programs by representing the former as the integer 9, and the | |
1146 latter as the symbol @code{tab}. | |
1147 | |
1148 Most of the time, it's not useful to distinguish the two. So normally | |
1149 @code{function-key-map} (@pxref{Translation Keymaps}) is set up to map | |
1150 @code{tab} into 9. Thus, a key binding for character code 9 (the | |
1151 character @kbd{C-i}) also applies to @code{tab}. Likewise for the other | |
1152 symbols in this group. The function @code{read-char} likewise converts | |
1153 these events into characters. | |
1154 | |
1155 In @acronym{ASCII}, @key{BS} is really @kbd{C-h}. But @code{backspace} | |
1156 converts into the character code 127 (@key{DEL}), not into code 8 | |
1157 (@key{BS}). This is what most users prefer. | |
1158 | |
1159 @item @code{left}, @code{up}, @code{right}, @code{down} | |
1160 Cursor arrow keys | |
1161 @item @code{kp-add}, @code{kp-decimal}, @code{kp-divide}, @dots{} | |
1162 Keypad keys (to the right of the regular keyboard). | |
1163 @item @code{kp-0}, @code{kp-1}, @dots{} | |
1164 Keypad keys with digits. | |
1165 @item @code{kp-f1}, @code{kp-f2}, @code{kp-f3}, @code{kp-f4} | |
1166 Keypad PF keys. | |
1167 @item @code{kp-home}, @code{kp-left}, @code{kp-up}, @code{kp-right}, @code{kp-down} | |
1168 Keypad arrow keys. Emacs normally translates these into the | |
1169 corresponding non-keypad keys @code{home}, @code{left}, @dots{} | |
1170 @item @code{kp-prior}, @code{kp-next}, @code{kp-end}, @code{kp-begin}, @code{kp-insert}, @code{kp-delete} | |
1171 Additional keypad duplicates of keys ordinarily found elsewhere. Emacs | |
1172 normally translates these into the like-named non-keypad keys. | |
1173 @end table | |
1174 | |
1175 You can use the modifier keys @key{ALT}, @key{CTRL}, @key{HYPER}, | |
1176 @key{META}, @key{SHIFT}, and @key{SUPER} with function keys. The way to | |
1177 represent them is with prefixes in the symbol name: | |
1178 | |
1179 @table @samp | |
1180 @item A- | |
1181 The alt modifier. | |
1182 @item C- | |
1183 The control modifier. | |
1184 @item H- | |
1185 The hyper modifier. | |
1186 @item M- | |
1187 The meta modifier. | |
1188 @item S- | |
1189 The shift modifier. | |
1190 @item s- | |
1191 The super modifier. | |
1192 @end table | |
1193 | |
1194 Thus, the symbol for the key @key{F3} with @key{META} held down is | |
1195 @code{M-f3}. When you use more than one prefix, we recommend you | |
1196 write them in alphabetical order; but the order does not matter in | |
1197 arguments to the key-binding lookup and modification functions. | |
1198 | |
1199 @node Mouse Events | |
1200 @subsection Mouse Events | |
1201 | |
1202 Emacs supports four kinds of mouse events: click events, drag events, | |
1203 button-down events, and motion events. All mouse events are represented | |
1204 as lists. The @sc{car} of the list is the event type; this says which | |
1205 mouse button was involved, and which modifier keys were used with it. | |
1206 The event type can also distinguish double or triple button presses | |
1207 (@pxref{Repeat Events}). The rest of the list elements give position | |
1208 and time information. | |
1209 | |
1210 For key lookup, only the event type matters: two events of the same type | |
1211 necessarily run the same command. The command can access the full | |
1212 values of these events using the @samp{e} interactive code. | |
1213 @xref{Interactive Codes}. | |
1214 | |
1215 A key sequence that starts with a mouse event is read using the keymaps | |
1216 of the buffer in the window that the mouse was in, not the current | |
1217 buffer. This does not imply that clicking in a window selects that | |
1218 window or its buffer---that is entirely under the control of the command | |
1219 binding of the key sequence. | |
1220 | |
1221 @node Click Events | |
1222 @subsection Click Events | |
1223 @cindex click event | |
1224 @cindex mouse click event | |
1225 | |
1226 When the user presses a mouse button and releases it at the same | |
1227 location, that generates a @dfn{click} event. All mouse click event | |
1228 share the same format: | |
1229 | |
1230 @example | |
1231 (@var{event-type} @var{position} @var{click-count}) | |
1232 @end example | |
1233 | |
1234 @table @asis | |
1235 @item @var{event-type} | |
1236 This is a symbol that indicates which mouse button was used. It is | |
1237 one of the symbols @code{mouse-1}, @code{mouse-2}, @dots{}, where the | |
1238 buttons are numbered left to right. | |
1239 | |
1240 You can also use prefixes @samp{A-}, @samp{C-}, @samp{H-}, @samp{M-}, | |
1241 @samp{S-} and @samp{s-} for modifiers alt, control, hyper, meta, shift | |
1242 and super, just as you would with function keys. | |
1243 | |
1244 This symbol also serves as the event type of the event. Key bindings | |
1245 describe events by their types; thus, if there is a key binding for | |
1246 @code{mouse-1}, that binding would apply to all events whose | |
1247 @var{event-type} is @code{mouse-1}. | |
1248 | |
1249 @item @var{position} | |
1250 This is the position where the mouse click occurred. The actual | |
1251 format of @var{position} depends on what part of a window was clicked | |
1252 on. | |
1253 | |
1254 For mouse click events in the text area, mode line, header line, or in | |
1255 the marginal areas, @var{position} has this form: | |
1256 | |
1257 @example | |
1258 (@var{window} @var{pos-or-area} (@var{x} . @var{y}) @var{timestamp} | |
1259 @var{object} @var{text-pos} (@var{col} . @var{row}) | |
1260 @var{image} (@var{dx} . @var{dy}) (@var{width} . @var{height})) | |
1261 @end example | |
1262 | |
1263 @table @asis | |
1264 @item @var{window} | |
1265 This is the window in which the click occurred. | |
1266 | |
1267 @item @var{pos-or-area} | |
1268 This is the buffer position of the character clicked on in the text | |
1269 area, or if clicked outside the text area, it is the window area in | |
1270 which the click occurred. It is one of the symbols @code{mode-line}, | |
1271 @code{header-line}, @code{vertical-line}, @code{left-margin}, | |
1272 @code{right-margin}, @code{left-fringe}, or @code{right-fringe}. | |
1273 | |
1274 In one special case, @var{pos-or-area} is a list containing a symbol (one | |
1275 of the symbols listed above) instead of just the symbol. This happens | |
1276 after the imaginary prefix keys for the event are inserted into the | |
1277 input stream. @xref{Key Sequence Input}. | |
1278 | |
1279 | |
1280 @item @var{x}, @var{y} | |
1281 These are the pixel coordinates of the click, relative to | |
1282 the top left corner of @var{window}, which is @code{(0 . 0)}. | |
1283 For the mode or header line, @var{y} does not have meaningful data. | |
1284 For the vertical line, @var{x} does not have meaningful data. | |
1285 | |
1286 @item @var{timestamp} | |
1287 This is the time at which the event occurred, in milliseconds. | |
1288 | |
1289 @item @var{object} | |
1290 This is the object on which the click occurred. It is either | |
1291 @code{nil} if there is no string property, or it has the form | |
1292 (@var{string} . @var{string-pos}) when there is a string-type text | |
1293 property at the click position. | |
1294 | |
1295 @table @asis | |
1296 @item @var{string} | |
1297 This is the string on which the click occurred, including any | |
1298 properties. | |
1299 | |
1300 @item @var{string-pos} | |
1301 This is the position in the string on which the click occurred, | |
1302 relevant if properties at the click need to be looked up. | |
1303 @end table | |
1304 | |
1305 @item @var{text-pos} | |
1306 For clicks on a marginal area or on a fringe, this is the buffer | |
1307 position of the first visible character in the corresponding line in | |
1308 the window. For other events, it is the current buffer position in | |
1309 the window. | |
1310 | |
1311 @item @var{col}, @var{row} | |
1312 These are the actual coordinates of the glyph under the @var{x}, | |
1313 @var{y} position, possibly padded with default character width | |
1314 glyphs if @var{x} is beyond the last glyph on the line. | |
1315 | |
1316 @item @var{image} | |
1317 This is the image object on which the click occurred. It is either | |
1318 @code{nil} if there is no image at the position clicked on, or it is | |
1319 an image object as returned by @code{find-image} if click was in an image. | |
1320 | |
1321 @item @var{dx}, @var{dy} | |
1322 These are the pixel coordinates of the click, relative to | |
1323 the top left corner of @var{object}, which is @code{(0 . 0)}. If | |
1324 @var{object} is @code{nil}, the coordinates are relative to the top | |
1325 left corner of the character glyph clicked on. | |
1326 | |
1327 @item @var{width}, @var{height} | |
1328 These are the pixel width and height of @var{object} or, if this is | |
1329 @code{nil}, those of the character glyph clicked on. | |
1330 @end table | |
1331 | |
1332 @sp 1 | |
1333 For mouse clicks on a scroll-bar, @var{position} has this form: | |
1334 | |
1335 @example | |
1336 (@var{window} @var{area} (@var{portion} . @var{whole}) @var{timestamp} @var{part}) | |
1337 @end example | |
1338 | |
1339 @table @asis | |
1340 @item @var{window} | |
1341 This is the window whose scroll-bar was clicked on. | |
1342 | |
1343 @item @var{area} | |
1344 This is the scroll bar where the click occurred. It is one of the | |
1345 symbols @code{vertical-scroll-bar} or @code{horizontal-scroll-bar}. | |
1346 | |
1347 @item @var{portion} | |
1348 This is the distance of the click from the top or left end of | |
1349 the scroll bar. | |
1350 | |
1351 @item @var{whole} | |
1352 This is the length of the entire scroll bar. | |
1353 | |
1354 @item @var{timestamp} | |
1355 This is the time at which the event occurred, in milliseconds. | |
1356 | |
1357 @item @var{part} | |
1358 This is the part of the scroll-bar which was clicked on. It is one | |
1359 of the symbols @code{above-handle}, @code{handle}, @code{below-handle}, | |
1360 @code{up}, @code{down}, @code{top}, @code{bottom}, and @code{end-scroll}. | |
1361 @end table | |
1362 | |
1363 @item @var{click-count} | |
1364 This is the number of rapid repeated presses so far of the same mouse | |
1365 button. @xref{Repeat Events}. | |
1366 @end table | |
1367 | |
1368 @node Drag Events | |
1369 @subsection Drag Events | |
1370 @cindex drag event | |
1371 @cindex mouse drag event | |
1372 | |
1373 With Emacs, you can have a drag event without even changing your | |
1374 clothes. A @dfn{drag event} happens every time the user presses a mouse | |
1375 button and then moves the mouse to a different character position before | |
1376 releasing the button. Like all mouse events, drag events are | |
1377 represented in Lisp as lists. The lists record both the starting mouse | |
1378 position and the final position, like this: | |
1379 | |
1380 @example | |
1381 (@var{event-type} | |
1382 (@var{window1} START-POSITION) | |
1383 (@var{window2} END-POSITION)) | |
1384 @end example | |
1385 | |
1386 For a drag event, the name of the symbol @var{event-type} contains the | |
1387 prefix @samp{drag-}. For example, dragging the mouse with button 2 | |
1388 held down generates a @code{drag-mouse-2} event. The second and third | |
1389 elements of the event give the starting and ending position of the | |
1390 drag. They have the same form as @var{position} in a click event | |
1391 (@pxref{Click Events}) that is not on the scroll bar part of the | |
1392 window. You can access the second element of any mouse event in the | |
1393 same way, with no need to distinguish drag events from others. | |
1394 | |
1395 The @samp{drag-} prefix follows the modifier key prefixes such as | |
1396 @samp{C-} and @samp{M-}. | |
1397 | |
1398 If @code{read-key-sequence} receives a drag event that has no key | |
1399 binding, and the corresponding click event does have a binding, it | |
1400 changes the drag event into a click event at the drag's starting | |
1401 position. This means that you don't have to distinguish between click | |
1402 and drag events unless you want to. | |
1403 | |
1404 @node Button-Down Events | |
1405 @subsection Button-Down Events | |
1406 @cindex button-down event | |
1407 | |
1408 Click and drag events happen when the user releases a mouse button. | |
1409 They cannot happen earlier, because there is no way to distinguish a | |
1410 click from a drag until the button is released. | |
1411 | |
1412 If you want to take action as soon as a button is pressed, you need to | |
1413 handle @dfn{button-down} events.@footnote{Button-down is the | |
1414 conservative antithesis of drag.} These occur as soon as a button is | |
1415 pressed. They are represented by lists that look exactly like click | |
1416 events (@pxref{Click Events}), except that the @var{event-type} symbol | |
1417 name contains the prefix @samp{down-}. The @samp{down-} prefix follows | |
1418 modifier key prefixes such as @samp{C-} and @samp{M-}. | |
1419 | |
1420 The function @code{read-key-sequence} ignores any button-down events | |
1421 that don't have command bindings; therefore, the Emacs command loop | |
1422 ignores them too. This means that you need not worry about defining | |
1423 button-down events unless you want them to do something. The usual | |
1424 reason to define a button-down event is so that you can track mouse | |
1425 motion (by reading motion events) until the button is released. | |
1426 @xref{Motion Events}. | |
1427 | |
1428 @node Repeat Events | |
1429 @subsection Repeat Events | |
1430 @cindex repeat events | |
1431 @cindex double-click events | |
1432 @cindex triple-click events | |
1433 @cindex mouse events, repeated | |
1434 | |
1435 If you press the same mouse button more than once in quick succession | |
1436 without moving the mouse, Emacs generates special @dfn{repeat} mouse | |
1437 events for the second and subsequent presses. | |
1438 | |
1439 The most common repeat events are @dfn{double-click} events. Emacs | |
1440 generates a double-click event when you click a button twice; the event | |
1441 happens when you release the button (as is normal for all click | |
1442 events). | |
1443 | |
1444 The event type of a double-click event contains the prefix | |
1445 @samp{double-}. Thus, a double click on the second mouse button with | |
1446 @key{meta} held down comes to the Lisp program as | |
1447 @code{M-double-mouse-2}. If a double-click event has no binding, the | |
1448 binding of the corresponding ordinary click event is used to execute | |
1449 it. Thus, you need not pay attention to the double click feature | |
1450 unless you really want to. | |
1451 | |
1452 When the user performs a double click, Emacs generates first an ordinary | |
1453 click event, and then a double-click event. Therefore, you must design | |
1454 the command binding of the double click event to assume that the | |
1455 single-click command has already run. It must produce the desired | |
1456 results of a double click, starting from the results of a single click. | |
1457 | |
1458 This is convenient, if the meaning of a double click somehow ``builds | |
1459 on'' the meaning of a single click---which is recommended user interface | |
1460 design practice for double clicks. | |
1461 | |
1462 If you click a button, then press it down again and start moving the | |
1463 mouse with the button held down, then you get a @dfn{double-drag} event | |
1464 when you ultimately release the button. Its event type contains | |
1465 @samp{double-drag} instead of just @samp{drag}. If a double-drag event | |
1466 has no binding, Emacs looks for an alternate binding as if the event | |
1467 were an ordinary drag. | |
1468 | |
1469 Before the double-click or double-drag event, Emacs generates a | |
1470 @dfn{double-down} event when the user presses the button down for the | |
1471 second time. Its event type contains @samp{double-down} instead of just | |
1472 @samp{down}. If a double-down event has no binding, Emacs looks for an | |
1473 alternate binding as if the event were an ordinary button-down event. | |
1474 If it finds no binding that way either, the double-down event is | |
1475 ignored. | |
1476 | |
1477 To summarize, when you click a button and then press it again right | |
1478 away, Emacs generates a down event and a click event for the first | |
1479 click, a double-down event when you press the button again, and finally | |
1480 either a double-click or a double-drag event. | |
1481 | |
1482 If you click a button twice and then press it again, all in quick | |
1483 succession, Emacs generates a @dfn{triple-down} event, followed by | |
1484 either a @dfn{triple-click} or a @dfn{triple-drag}. The event types of | |
1485 these events contain @samp{triple} instead of @samp{double}. If any | |
1486 triple event has no binding, Emacs uses the binding that it would use | |
1487 for the corresponding double event. | |
1488 | |
1489 If you click a button three or more times and then press it again, the | |
1490 events for the presses beyond the third are all triple events. Emacs | |
1491 does not have separate event types for quadruple, quintuple, etc.@: | |
1492 events. However, you can look at the event list to find out precisely | |
1493 how many times the button was pressed. | |
1494 | |
1495 @defun event-click-count event | |
1496 This function returns the number of consecutive button presses that led | |
1497 up to @var{event}. If @var{event} is a double-down, double-click or | |
1498 double-drag event, the value is 2. If @var{event} is a triple event, | |
1499 the value is 3 or greater. If @var{event} is an ordinary mouse event | |
1500 (not a repeat event), the value is 1. | |
1501 @end defun | |
1502 | |
1503 @defopt double-click-fuzz | |
1504 To generate repeat events, successive mouse button presses must be at | |
1505 approximately the same screen position. The value of | |
1506 @code{double-click-fuzz} specifies the maximum number of pixels the | |
1507 mouse may be moved (horizontally or vertically) between two successive | |
1508 clicks to make a double-click. | |
1509 | |
1510 This variable is also the threshold for motion of the mouse to count | |
1511 as a drag. | |
1512 @end defopt | |
1513 | |
1514 @defopt double-click-time | |
1515 To generate repeat events, the number of milliseconds between | |
1516 successive button presses must be less than the value of | |
1517 @code{double-click-time}. Setting @code{double-click-time} to | |
1518 @code{nil} disables multi-click detection entirely. Setting it to | |
1519 @code{t} removes the time limit; Emacs then detects multi-clicks by | |
1520 position only. | |
1521 @end defopt | |
1522 | |
1523 @node Motion Events | |
1524 @subsection Motion Events | |
1525 @cindex motion event | |
1526 @cindex mouse motion events | |
1527 | |
1528 Emacs sometimes generates @dfn{mouse motion} events to describe motion | |
1529 of the mouse without any button activity. Mouse motion events are | |
1530 represented by lists that look like this: | |
1531 | |
1532 @example | |
1533 (mouse-movement (POSITION)) | |
1534 @end example | |
1535 | |
1536 The second element of the list describes the current position of the | |
1537 mouse, just as in a click event (@pxref{Click Events}). | |
1538 | |
1539 The special form @code{track-mouse} enables generation of motion events | |
1540 within its body. Outside of @code{track-mouse} forms, Emacs does not | |
1541 generate events for mere motion of the mouse, and these events do not | |
1542 appear. @xref{Mouse Tracking}. | |
1543 | |
1544 @node Focus Events | |
1545 @subsection Focus Events | |
1546 @cindex focus event | |
1547 | |
1548 Window systems provide general ways for the user to control which window | |
1549 gets keyboard input. This choice of window is called the @dfn{focus}. | |
1550 When the user does something to switch between Emacs frames, that | |
1551 generates a @dfn{focus event}. The normal definition of a focus event, | |
1552 in the global keymap, is to select a new frame within Emacs, as the user | |
1553 would expect. @xref{Input Focus}. | |
1554 | |
1555 Focus events are represented in Lisp as lists that look like this: | |
1556 | |
1557 @example | |
1558 (switch-frame @var{new-frame}) | |
1559 @end example | |
1560 | |
1561 @noindent | |
1562 where @var{new-frame} is the frame switched to. | |
1563 | |
1564 Most X window managers are set up so that just moving the mouse into a | |
1565 window is enough to set the focus there. Emacs appears to do this, | |
1566 because it changes the cursor to solid in the new frame. However, there | |
1567 is no need for the Lisp program to know about the focus change until | |
1568 some other kind of input arrives. So Emacs generates a focus event only | |
1569 when the user actually types a keyboard key or presses a mouse button in | |
1570 the new frame; just moving the mouse between frames does not generate a | |
1571 focus event. | |
1572 | |
1573 A focus event in the middle of a key sequence would garble the | |
1574 sequence. So Emacs never generates a focus event in the middle of a key | |
1575 sequence. If the user changes focus in the middle of a key | |
1576 sequence---that is, after a prefix key---then Emacs reorders the events | |
1577 so that the focus event comes either before or after the multi-event key | |
1578 sequence, and not within it. | |
1579 | |
1580 @node Misc Events | |
1581 @subsection Miscellaneous System Events | |
1582 | |
1583 A few other event types represent occurrences within the system. | |
1584 | |
1585 @table @code | |
1586 @cindex @code{delete-frame} event | |
1587 @item (delete-frame (@var{frame})) | |
1588 This kind of event indicates that the user gave the window manager | |
1589 a command to delete a particular window, which happens to be an Emacs frame. | |
1590 | |
1591 The standard definition of the @code{delete-frame} event is to delete @var{frame}. | |
1592 | |
1593 @cindex @code{iconify-frame} event | |
1594 @item (iconify-frame (@var{frame})) | |
1595 This kind of event indicates that the user iconified @var{frame} using | |
1596 the window manager. Its standard definition is @code{ignore}; since the | |
1597 frame has already been iconified, Emacs has no work to do. The purpose | |
1598 of this event type is so that you can keep track of such events if you | |
1599 want to. | |
1600 | |
1601 @cindex @code{make-frame-visible} event | |
1602 @item (make-frame-visible (@var{frame})) | |
1603 This kind of event indicates that the user deiconified @var{frame} using | |
1604 the window manager. Its standard definition is @code{ignore}; since the | |
1605 frame has already been made visible, Emacs has no work to do. | |
1606 | |
1607 @cindex @code{wheel-up} event | |
1608 @cindex @code{wheel-down} event | |
1609 @item (wheel-up @var{position}) | |
1610 @item (wheel-down @var{position}) | |
1611 These kinds of event are generated by moving a mouse wheel. Their | |
1612 usual meaning is a kind of scroll or zoom. | |
1613 | |
1614 The element @var{position} is a list describing the position of the | |
1615 event, in the same format as used in a mouse-click event. | |
1616 | |
1617 This kind of event is generated only on some kinds of systems. On some | |
1618 systems, @code{mouse-4} and @code{mouse-5} are used instead. For | |
1619 portable code, use the variables @code{mouse-wheel-up-event} and | |
1620 @code{mouse-wheel-down-event} defined in @file{mwheel.el} to determine | |
1621 what event types to expect for the mouse wheel. | |
1622 | |
1623 @cindex @code{drag-n-drop} event | |
1624 @item (drag-n-drop @var{position} @var{files}) | |
1625 This kind of event is generated when a group of files is | |
1626 selected in an application outside of Emacs, and then dragged and | |
1627 dropped onto an Emacs frame. | |
1628 | |
1629 The element @var{position} is a list describing the position of the | |
1630 event, in the same format as used in a mouse-click event, and | |
1631 @var{files} is the list of file names that were dragged and dropped. | |
1632 The usual way to handle this event is by visiting these files. | |
1633 | |
1634 This kind of event is generated, at present, only on some kinds of | |
1635 systems. | |
1636 | |
1637 @cindex @code{help-echo} event | |
1638 @item help-echo | |
1639 This kind of event is generated when a mouse pointer moves onto a | |
1640 portion of buffer text which has a @code{help-echo} text property. | |
1641 The generated event has this form: | |
1642 | |
1643 @example | |
1644 (help-echo @var{frame} @var{help} @var{window} @var{object} @var{pos}) | |
1645 @end example | |
1646 | |
1647 @noindent | |
1648 The precise meaning of the event parameters and the way these | |
1649 parameters are used to display the help-echo text are described in | |
1650 @ref{Text help-echo}. | |
1651 | |
1652 @cindex @code{sigusr1} event | |
1653 @cindex @code{sigusr2} event | |
1654 @cindex user signals | |
1655 @item sigusr1 | |
1656 @itemx sigusr2 | |
1657 These events are generated when the Emacs process receives | |
1658 the signals @code{SIGUSR1} and @code{SIGUSR2}. They contain no | |
1659 additional data because signals do not carry additional information. | |
1660 | |
1661 To catch a user signal, bind the corresponding event to an interactive | |
1662 command in the @code{special-event-map} (@pxref{Active Keymaps}). | |
1663 The command is called with no arguments, and the specific signal event is | |
1664 available in @code{last-input-event}. For example: | |
1665 | |
1666 @smallexample | |
1667 (defun sigusr-handler () | |
1668 (interactive) | |
1669 (message "Caught signal %S" last-input-event)) | |
1670 | |
1671 (define-key special-event-map [sigusr1] 'sigusr-handler) | |
1672 @end smallexample | |
1673 | |
1674 To test the signal handler, you can make Emacs send a signal to itself: | |
1675 | |
1676 @smallexample | |
1677 (signal-process (emacs-pid) 'sigusr1) | |
1678 @end smallexample | |
1679 @end table | |
1680 | |
1681 If one of these events arrives in the middle of a key sequence---that | |
1682 is, after a prefix key---then Emacs reorders the events so that this | |
1683 event comes either before or after the multi-event key sequence, not | |
1684 within it. | |
1685 | |
1686 @node Event Examples | |
1687 @subsection Event Examples | |
1688 | |
1689 If the user presses and releases the left mouse button over the same | |
1690 location, that generates a sequence of events like this: | |
1691 | |
1692 @smallexample | |
1693 (down-mouse-1 (#<window 18 on NEWS> 2613 (0 . 38) -864320)) | |
1694 (mouse-1 (#<window 18 on NEWS> 2613 (0 . 38) -864180)) | |
1695 @end smallexample | |
1696 | |
1697 While holding the control key down, the user might hold down the | |
1698 second mouse button, and drag the mouse from one line to the next. | |
1699 That produces two events, as shown here: | |
1700 | |
1701 @smallexample | |
1702 (C-down-mouse-2 (#<window 18 on NEWS> 3440 (0 . 27) -731219)) | |
1703 (C-drag-mouse-2 (#<window 18 on NEWS> 3440 (0 . 27) -731219) | |
1704 (#<window 18 on NEWS> 3510 (0 . 28) -729648)) | |
1705 @end smallexample | |
1706 | |
1707 While holding down the meta and shift keys, the user might press the | |
1708 second mouse button on the window's mode line, and then drag the mouse | |
1709 into another window. That produces a pair of events like these: | |
1710 | |
1711 @smallexample | |
1712 (M-S-down-mouse-2 (#<window 18 on NEWS> mode-line (33 . 31) -457844)) | |
1713 (M-S-drag-mouse-2 (#<window 18 on NEWS> mode-line (33 . 31) -457844) | |
1714 (#<window 20 on carlton-sanskrit.tex> 161 (33 . 3) | |
1715 -453816)) | |
1716 @end smallexample | |
1717 | |
1718 To handle a SIGUSR1 signal, define an interactive function, and | |
1719 bind it to the @code{signal usr1} event sequence: | |
1720 | |
1721 @smallexample | |
1722 (defun usr1-handler () | |
1723 (interactive) | |
1724 (message "Got USR1 signal")) | |
1725 (global-set-key [signal usr1] 'usr1-handler) | |
1726 @end smallexample | |
1727 | |
1728 @node Classifying Events | |
1729 @subsection Classifying Events | |
1730 @cindex event type | |
1731 | |
1732 Every event has an @dfn{event type}, which classifies the event for | |
1733 key binding purposes. For a keyboard event, the event type equals the | |
1734 event value; thus, the event type for a character is the character, and | |
1735 the event type for a function key symbol is the symbol itself. For | |
1736 events that are lists, the event type is the symbol in the @sc{car} of | |
1737 the list. Thus, the event type is always a symbol or a character. | |
1738 | |
1739 Two events of the same type are equivalent where key bindings are | |
1740 concerned; thus, they always run the same command. That does not | |
1741 necessarily mean they do the same things, however, as some commands look | |
1742 at the whole event to decide what to do. For example, some commands use | |
1743 the location of a mouse event to decide where in the buffer to act. | |
1744 | |
1745 Sometimes broader classifications of events are useful. For example, | |
1746 you might want to ask whether an event involved the @key{META} key, | |
1747 regardless of which other key or mouse button was used. | |
1748 | |
1749 The functions @code{event-modifiers} and @code{event-basic-type} are | |
1750 provided to get such information conveniently. | |
1751 | |
1752 @defun event-modifiers event | |
1753 This function returns a list of the modifiers that @var{event} has. The | |
1754 modifiers are symbols; they include @code{shift}, @code{control}, | |
1755 @code{meta}, @code{alt}, @code{hyper} and @code{super}. In addition, | |
1756 the modifiers list of a mouse event symbol always contains one of | |
1757 @code{click}, @code{drag}, and @code{down}. For double or triple | |
1758 events, it also contains @code{double} or @code{triple}. | |
1759 | |
1760 The argument @var{event} may be an entire event object, or just an | |
1761 event type. If @var{event} is a symbol that has never been used in an | |
1762 event that has been read as input in the current Emacs session, then | |
1763 @code{event-modifiers} can return @code{nil}, even when @var{event} | |
1764 actually has modifiers. | |
1765 | |
1766 Here are some examples: | |
1767 | |
1768 @example | |
1769 (event-modifiers ?a) | |
1770 @result{} nil | |
1771 (event-modifiers ?A) | |
1772 @result{} (shift) | |
1773 (event-modifiers ?\C-a) | |
1774 @result{} (control) | |
1775 (event-modifiers ?\C-%) | |
1776 @result{} (control) | |
1777 (event-modifiers ?\C-\S-a) | |
1778 @result{} (control shift) | |
1779 (event-modifiers 'f5) | |
1780 @result{} nil | |
1781 (event-modifiers 's-f5) | |
1782 @result{} (super) | |
1783 (event-modifiers 'M-S-f5) | |
1784 @result{} (meta shift) | |
1785 (event-modifiers 'mouse-1) | |
1786 @result{} (click) | |
1787 (event-modifiers 'down-mouse-1) | |
1788 @result{} (down) | |
1789 @end example | |
1790 | |
1791 The modifiers list for a click event explicitly contains @code{click}, | |
1792 but the event symbol name itself does not contain @samp{click}. | |
1793 @end defun | |
1794 | |
1795 @defun event-basic-type event | |
1796 This function returns the key or mouse button that @var{event} | |
1797 describes, with all modifiers removed. The @var{event} argument is as | |
1798 in @code{event-modifiers}. For example: | |
1799 | |
1800 @example | |
1801 (event-basic-type ?a) | |
1802 @result{} 97 | |
1803 (event-basic-type ?A) | |
1804 @result{} 97 | |
1805 (event-basic-type ?\C-a) | |
1806 @result{} 97 | |
1807 (event-basic-type ?\C-\S-a) | |
1808 @result{} 97 | |
1809 (event-basic-type 'f5) | |
1810 @result{} f5 | |
1811 (event-basic-type 's-f5) | |
1812 @result{} f5 | |
1813 (event-basic-type 'M-S-f5) | |
1814 @result{} f5 | |
1815 (event-basic-type 'down-mouse-1) | |
1816 @result{} mouse-1 | |
1817 @end example | |
1818 @end defun | |
1819 | |
1820 @defun mouse-movement-p object | |
1821 This function returns non-@code{nil} if @var{object} is a mouse movement | |
1822 event. | |
1823 @end defun | |
1824 | |
1825 @defun event-convert-list list | |
1826 This function converts a list of modifier names and a basic event type | |
1827 to an event type which specifies all of them. The basic event type | |
1828 must be the last element of the list. For example, | |
1829 | |
1830 @example | |
1831 (event-convert-list '(control ?a)) | |
1832 @result{} 1 | |
1833 (event-convert-list '(control meta ?a)) | |
1834 @result{} -134217727 | |
1835 (event-convert-list '(control super f1)) | |
1836 @result{} C-s-f1 | |
1837 @end example | |
1838 @end defun | |
1839 | |
87519
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
1840 @node Accessing Mouse |
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
1841 @subsection Accessing Mouse Events |
84053 | 1842 @cindex mouse events, data in |
1843 | |
1844 This section describes convenient functions for accessing the data in | |
1845 a mouse button or motion event. | |
1846 | |
1847 These two functions return the starting or ending position of a | |
1848 mouse-button event, as a list of this form: | |
1849 | |
1850 @example | |
1851 (@var{window} @var{pos-or-area} (@var{x} . @var{y}) @var{timestamp} | |
1852 @var{object} @var{text-pos} (@var{col} . @var{row}) | |
1853 @var{image} (@var{dx} . @var{dy}) (@var{width} . @var{height})) | |
1854 @end example | |
1855 | |
1856 @defun event-start event | |
1857 This returns the starting position of @var{event}. | |
1858 | |
1859 If @var{event} is a click or button-down event, this returns the | |
1860 location of the event. If @var{event} is a drag event, this returns the | |
1861 drag's starting position. | |
1862 @end defun | |
1863 | |
1864 @defun event-end event | |
1865 This returns the ending position of @var{event}. | |
1866 | |
1867 If @var{event} is a drag event, this returns the position where the user | |
1868 released the mouse button. If @var{event} is a click or button-down | |
1869 event, the value is actually the starting position, which is the only | |
1870 position such events have. | |
1871 @end defun | |
1872 | |
1873 @cindex mouse position list, accessing | |
1874 These functions take a position list as described above, and | |
1875 return various parts of it. | |
1876 | |
1877 @defun posn-window position | |
1878 Return the window that @var{position} is in. | |
1879 @end defun | |
1880 | |
1881 @defun posn-area position | |
1882 Return the window area recorded in @var{position}. It returns @code{nil} | |
1883 when the event occurred in the text area of the window; otherwise, it | |
1884 is a symbol identifying the area in which the event occurred. | |
1885 @end defun | |
1886 | |
1887 @defun posn-point position | |
1888 Return the buffer position in @var{position}. When the event occurred | |
1889 in the text area of the window, in a marginal area, or on a fringe, | |
1890 this is an integer specifying a buffer position. Otherwise, the value | |
1891 is undefined. | |
1892 @end defun | |
1893 | |
1894 @defun posn-x-y position | |
1895 Return the pixel-based x and y coordinates in @var{position}, as a | |
1896 cons cell @code{(@var{x} . @var{y})}. These coordinates are relative | |
1897 to the window given by @code{posn-window}. | |
1898 | |
1899 This example shows how to convert these window-relative coordinates | |
1900 into frame-relative coordinates: | |
1901 | |
1902 @example | |
1903 (defun frame-relative-coordinates (position) | |
1904 "Return frame-relative coordinates from POSITION." | |
1905 (let* ((x-y (posn-x-y position)) | |
1906 (window (posn-window position)) | |
1907 (edges (window-inside-pixel-edges window))) | |
1908 (cons (+ (car x-y) (car edges)) | |
1909 (+ (cdr x-y) (cadr edges))))) | |
1910 @end example | |
1911 @end defun | |
1912 | |
1913 @defun posn-col-row position | |
1914 Return the row and column (in units of the frame's default character | |
1915 height and width) of @var{position}, as a cons cell @code{(@var{col} . | |
1916 @var{row})}. These are computed from the @var{x} and @var{y} values | |
1917 actually found in @var{position}. | |
1918 @end defun | |
1919 | |
1920 @defun posn-actual-col-row position | |
1921 Return the actual row and column in @var{position}, as a cons cell | |
1922 @code{(@var{col} . @var{row})}. The values are the actual row number | |
1923 in the window, and the actual character number in that row. It returns | |
1924 @code{nil} if @var{position} does not include actual positions values. | |
1925 You can use @code{posn-col-row} to get approximate values. | |
1926 @end defun | |
1927 | |
1928 @defun posn-string position | |
1929 Return the string object in @var{position}, either @code{nil}, or a | |
1930 cons cell @code{(@var{string} . @var{string-pos})}. | |
1931 @end defun | |
1932 | |
1933 @defun posn-image position | |
1934 Return the image object in @var{position}, either @code{nil}, or an | |
1935 image @code{(image ...)}. | |
1936 @end defun | |
1937 | |
1938 @defun posn-object position | |
1939 Return the image or string object in @var{position}, either | |
1940 @code{nil}, an image @code{(image ...)}, or a cons cell | |
1941 @code{(@var{string} . @var{string-pos})}. | |
1942 @end defun | |
1943 | |
1944 @defun posn-object-x-y position | |
1945 Return the pixel-based x and y coordinates relative to the upper left | |
1946 corner of the object in @var{position} as a cons cell @code{(@var{dx} | |
1947 . @var{dy})}. If the @var{position} is a buffer position, return the | |
1948 relative position in the character at that position. | |
1949 @end defun | |
1950 | |
1951 @defun posn-object-width-height position | |
1952 Return the pixel width and height of the object in @var{position} as a | |
1953 cons cell @code{(@var{width} . @var{height})}. If the @var{position} | |
1954 is a buffer position, return the size of the character at that position. | |
1955 @end defun | |
1956 | |
1957 @cindex timestamp of a mouse event | |
1958 @defun posn-timestamp position | |
1959 Return the timestamp in @var{position}. This is the time at which the | |
1960 event occurred, in milliseconds. | |
1961 @end defun | |
1962 | |
1963 These functions compute a position list given particular buffer | |
1964 position or screen position. You can access the data in this position | |
1965 list with the functions described above. | |
1966 | |
1967 @defun posn-at-point &optional pos window | |
1968 This function returns a position list for position @var{pos} in | |
1969 @var{window}. @var{pos} defaults to point in @var{window}; | |
1970 @var{window} defaults to the selected window. | |
1971 | |
1972 @code{posn-at-point} returns @code{nil} if @var{pos} is not visible in | |
1973 @var{window}. | |
1974 @end defun | |
1975 | |
1976 @defun posn-at-x-y x y &optional frame-or-window whole | |
1977 This function returns position information corresponding to pixel | |
1978 coordinates @var{x} and @var{y} in a specified frame or window, | |
1979 @var{frame-or-window}, which defaults to the selected window. | |
1980 The coordinates @var{x} and @var{y} are relative to the | |
1981 frame or window used. | |
1982 If @var{whole} is @code{nil}, the coordinates are relative | |
1983 to the window text area, otherwise they are relative to | |
1984 the entire window area including scroll bars, margins and fringes. | |
1985 @end defun | |
1986 | |
87519
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
1987 @node Accessing Scroll |
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
1988 @subsection Accessing Scroll Bar Events |
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
1989 @cindex scroll bar events, data in |
6a0c500ca3a9
Merge from emacs--rel--22, gnus--devo--0
Miles Bader <miles@gnu.org>
parents:
85311
diff
changeset
|
1990 |
84053 | 1991 These functions are useful for decoding scroll bar events. |
1992 | |
1993 @defun scroll-bar-event-ratio event | |
1994 This function returns the fractional vertical position of a scroll bar | |
1995 event within the scroll bar. The value is a cons cell | |
1996 @code{(@var{portion} . @var{whole})} containing two integers whose ratio | |
1997 is the fractional position. | |
1998 @end defun | |
1999 | |
2000 @defun scroll-bar-scale ratio total | |
2001 This function multiplies (in effect) @var{ratio} by @var{total}, | |
2002 rounding the result to an integer. The argument @var{ratio} is not a | |
2003 number, but rather a pair @code{(@var{num} . @var{denom})}---typically a | |
2004 value returned by @code{scroll-bar-event-ratio}. | |
2005 | |
2006 This function is handy for scaling a position on a scroll bar into a | |
2007 buffer position. Here's how to do that: | |
2008 | |
2009 @example | |
2010 (+ (point-min) | |
2011 (scroll-bar-scale | |
2012 (posn-x-y (event-start event)) | |
2013 (- (point-max) (point-min)))) | |
2014 @end example | |
2015 | |
2016 Recall that scroll bar events have two integers forming a ratio, in place | |
2017 of a pair of x and y coordinates. | |
2018 @end defun | |
2019 | |
2020 @node Strings of Events | |
2021 @subsection Putting Keyboard Events in Strings | |
2022 @cindex keyboard events in strings | |
2023 @cindex strings with keyboard events | |
2024 | |
2025 In most of the places where strings are used, we conceptualize the | |
2026 string as containing text characters---the same kind of characters found | |
2027 in buffers or files. Occasionally Lisp programs use strings that | |
2028 conceptually contain keyboard characters; for example, they may be key | |
2029 sequences or keyboard macro definitions. However, storing keyboard | |
2030 characters in a string is a complex matter, for reasons of historical | |
2031 compatibility, and it is not always possible. | |
2032 | |
2033 We recommend that new programs avoid dealing with these complexities | |
2034 by not storing keyboard events in strings. Here is how to do that: | |
2035 | |
2036 @itemize @bullet | |
2037 @item | |
2038 Use vectors instead of strings for key sequences, when you plan to use | |
2039 them for anything other than as arguments to @code{lookup-key} and | |
2040 @code{define-key}. For example, you can use | |
2041 @code{read-key-sequence-vector} instead of @code{read-key-sequence}, and | |
2042 @code{this-command-keys-vector} instead of @code{this-command-keys}. | |
2043 | |
2044 @item | |
2045 Use vectors to write key sequence constants containing meta characters, | |
2046 even when passing them directly to @code{define-key}. | |
2047 | |
2048 @item | |
2049 When you have to look at the contents of a key sequence that might be a | |
2050 string, use @code{listify-key-sequence} (@pxref{Event Input Misc}) | |
2051 first, to convert it to a list. | |
2052 @end itemize | |
2053 | |
2054 The complexities stem from the modifier bits that keyboard input | |
2055 characters can include. Aside from the Meta modifier, none of these | |
2056 modifier bits can be included in a string, and the Meta modifier is | |
2057 allowed only in special cases. | |
2058 | |
2059 The earliest GNU Emacs versions represented meta characters as codes | |
2060 in the range of 128 to 255. At that time, the basic character codes | |
2061 ranged from 0 to 127, so all keyboard character codes did fit in a | |
2062 string. Many Lisp programs used @samp{\M-} in string constants to stand | |
2063 for meta characters, especially in arguments to @code{define-key} and | |
2064 similar functions, and key sequences and sequences of events were always | |
2065 represented as strings. | |
2066 | |
2067 When we added support for larger basic character codes beyond 127, and | |
2068 additional modifier bits, we had to change the representation of meta | |
2069 characters. Now the flag that represents the Meta modifier in a | |
2070 character is | |
2071 @tex | |
2072 @math{2^{27}} | |
2073 @end tex | |
2074 @ifnottex | |
2075 2**27 | |
2076 @end ifnottex | |
2077 and such numbers cannot be included in a string. | |
2078 | |
2079 To support programs with @samp{\M-} in string constants, there are | |
2080 special rules for including certain meta characters in a string. | |
2081 Here are the rules for interpreting a string as a sequence of input | |
2082 characters: | |
2083 | |
2084 @itemize @bullet | |
2085 @item | |
2086 If the keyboard character value is in the range of 0 to 127, it can go | |
2087 in the string unchanged. | |
2088 | |
2089 @item | |
2090 The meta variants of those characters, with codes in the range of | |
2091 @tex | |
2092 @math{2^{27}} | |
2093 @end tex | |
2094 @ifnottex | |
2095 2**27 | |
2096 @end ifnottex | |
2097 to | |
2098 @tex | |
2099 @math{2^{27} + 127}, | |
2100 @end tex | |
2101 @ifnottex | |
2102 2**27+127, | |
2103 @end ifnottex | |
2104 can also go in the string, but you must change their | |
2105 numeric values. You must set the | |
2106 @tex | |
2107 @math{2^{7}} | |
2108 @end tex | |
2109 @ifnottex | |
2110 2**7 | |
2111 @end ifnottex | |
2112 bit instead of the | |
2113 @tex | |
2114 @math{2^{27}} | |
2115 @end tex | |
2116 @ifnottex | |
2117 2**27 | |
2118 @end ifnottex | |
2119 bit, resulting in a value between 128 and 255. Only a unibyte string | |
2120 can include these codes. | |
2121 | |
2122 @item | |
2123 Non-@acronym{ASCII} characters above 256 can be included in a multibyte string. | |
2124 | |
2125 @item | |
2126 Other keyboard character events cannot fit in a string. This includes | |
2127 keyboard events in the range of 128 to 255. | |
2128 @end itemize | |
2129 | |
2130 Functions such as @code{read-key-sequence} that construct strings of | |
2131 keyboard input characters follow these rules: they construct vectors | |
2132 instead of strings, when the events won't fit in a string. | |
2133 | |
2134 When you use the read syntax @samp{\M-} in a string, it produces a | |
2135 code in the range of 128 to 255---the same code that you get if you | |
2136 modify the corresponding keyboard event to put it in the string. Thus, | |
2137 meta events in strings work consistently regardless of how they get into | |
2138 the strings. | |
2139 | |
2140 However, most programs would do well to avoid these issues by | |
2141 following the recommendations at the beginning of this section. | |
2142 | |
2143 @node Reading Input | |
2144 @section Reading Input | |
2145 @cindex read input | |
2146 @cindex keyboard input | |
2147 | |
2148 The editor command loop reads key sequences using the function | |
2149 @code{read-key-sequence}, which uses @code{read-event}. These and other | |
2150 functions for event input are also available for use in Lisp programs. | |
2151 See also @code{momentary-string-display} in @ref{Temporary Displays}, | |
2152 and @code{sit-for} in @ref{Waiting}. @xref{Terminal Input}, for | |
2153 functions and variables for controlling terminal input modes and | |
2154 debugging terminal input. | |
2155 | |
2156 For higher-level input facilities, see @ref{Minibuffers}. | |
2157 | |
2158 @menu | |
2159 * Key Sequence Input:: How to read one key sequence. | |
2160 * Reading One Event:: How to read just one event. | |
2161 * Event Mod:: How Emacs modifies events as they are read. | |
2162 * Invoking the Input Method:: How reading an event uses the input method. | |
2163 * Quoted Character Input:: Asking the user to specify a character. | |
2164 * Event Input Misc:: How to reread or throw away input events. | |
2165 @end menu | |
2166 | |
2167 @node Key Sequence Input | |
2168 @subsection Key Sequence Input | |
2169 @cindex key sequence input | |
2170 | |
2171 The command loop reads input a key sequence at a time, by calling | |
2172 @code{read-key-sequence}. Lisp programs can also call this function; | |
2173 for example, @code{describe-key} uses it to read the key to describe. | |
2174 | |
2175 @defun read-key-sequence prompt &optional continue-echo dont-downcase-last switch-frame-ok command-loop | |
2176 This function reads a key sequence and returns it as a string or | |
2177 vector. It keeps reading events until it has accumulated a complete key | |
2178 sequence; that is, enough to specify a non-prefix command using the | |
2179 currently active keymaps. (Remember that a key sequence that starts | |
2180 with a mouse event is read using the keymaps of the buffer in the | |
2181 window that the mouse was in, not the current buffer.) | |
2182 | |
2183 If the events are all characters and all can fit in a string, then | |
2184 @code{read-key-sequence} returns a string (@pxref{Strings of Events}). | |
2185 Otherwise, it returns a vector, since a vector can hold all kinds of | |
2186 events---characters, symbols, and lists. The elements of the string or | |
2187 vector are the events in the key sequence. | |
2188 | |
2189 Reading a key sequence includes translating the events in various | |
2190 ways. @xref{Translation Keymaps}. | |
2191 | |
2192 The argument @var{prompt} is either a string to be displayed in the | |
2193 echo area as a prompt, or @code{nil}, meaning not to display a prompt. | |
2194 The argument @var{continue-echo}, if non-@code{nil}, means to echo | |
2195 this key as a continuation of the previous key. | |
2196 | |
2197 Normally any upper case event is converted to lower case if the | |
2198 original event is undefined and the lower case equivalent is defined. | |
2199 The argument @var{dont-downcase-last}, if non-@code{nil}, means do not | |
2200 convert the last event to lower case. This is appropriate for reading | |
2201 a key sequence to be defined. | |
2202 | |
2203 The argument @var{switch-frame-ok}, if non-@code{nil}, means that this | |
2204 function should process a @code{switch-frame} event if the user | |
2205 switches frames before typing anything. If the user switches frames | |
2206 in the middle of a key sequence, or at the start of the sequence but | |
2207 @var{switch-frame-ok} is @code{nil}, then the event will be put off | |
2208 until after the current key sequence. | |
2209 | |
2210 The argument @var{command-loop}, if non-@code{nil}, means that this | |
2211 key sequence is being read by something that will read commands one | |
2212 after another. It should be @code{nil} if the caller will read just | |
2213 one key sequence. | |
2214 | |
2215 In the following example, Emacs displays the prompt @samp{?} in the | |
2216 echo area, and then the user types @kbd{C-x C-f}. | |
2217 | |
2218 @example | |
2219 (read-key-sequence "?") | |
2220 | |
2221 @group | |
2222 ---------- Echo Area ---------- | |
2223 ?@kbd{C-x C-f} | |
2224 ---------- Echo Area ---------- | |
2225 | |
2226 @result{} "^X^F" | |
2227 @end group | |
2228 @end example | |
2229 | |
2230 The function @code{read-key-sequence} suppresses quitting: @kbd{C-g} | |
2231 typed while reading with this function works like any other character, | |
2232 and does not set @code{quit-flag}. @xref{Quitting}. | |
2233 @end defun | |
2234 | |
2235 @defun read-key-sequence-vector prompt &optional continue-echo dont-downcase-last switch-frame-ok command-loop | |
2236 This is like @code{read-key-sequence} except that it always | |
2237 returns the key sequence as a vector, never as a string. | |
2238 @xref{Strings of Events}. | |
2239 @end defun | |
2240 | |
2241 @cindex upper case key sequence | |
2242 @cindex downcasing in @code{lookup-key} | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2243 @cindex shift-translation |
84053 | 2244 If an input character is upper-case (or has the shift modifier) and |
2245 has no key binding, but its lower-case equivalent has one, then | |
2246 @code{read-key-sequence} converts the character to lower case. Note | |
2247 that @code{lookup-key} does not perform case conversion in this way. | |
2248 | |
98751
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2249 @vindex this-command-keys-shift-translated |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2250 When reading input results in such a @dfn{shift-translation}, Emacs |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2251 sets the variable @code{this-command-keys-shift-translated} to a |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2252 non-nil value. Lisp programs can examine this variable if they need |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2253 to modify their behavior when invoked by shift-translated keys. For |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2254 example, the function @code{handle-shift-selection} examines the value |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2255 of this variable to determine how to activate or deactivate the region |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2256 (@pxref{The Mark, handle-shift-selection}). |
a0e705c1e7f7
(Using Interactive, Interactive Codes): Document `^'.
Eli Zaretskii <eliz@gnu.org>
parents:
94331
diff
changeset
|
2257 |
84053 | 2258 The function @code{read-key-sequence} also transforms some mouse events. |
2259 It converts unbound drag events into click events, and discards unbound | |
2260 button-down events entirely. It also reshuffles focus events and | |
2261 miscellaneous window events so that they never appear in a key sequence | |
2262 with any other events. | |
2263 | |
2264 @cindex @code{header-line} prefix key | |
2265 @cindex @code{mode-line} prefix key | |
2266 @cindex @code{vertical-line} prefix key | |
2267 @cindex @code{horizontal-scroll-bar} prefix key | |
2268 @cindex @code{vertical-scroll-bar} prefix key | |
2269 @cindex @code{menu-bar} prefix key | |
2270 @cindex mouse events, in special parts of frame | |
2271 When mouse events occur in special parts of a window, such as a mode | |
2272 line or a scroll bar, the event type shows nothing special---it is the | |
2273 same symbol that would normally represent that combination of mouse | |
2274 button and modifier keys. The information about the window part is kept | |
2275 elsewhere in the event---in the coordinates. But | |
2276 @code{read-key-sequence} translates this information into imaginary | |
2277 ``prefix keys,'' all of which are symbols: @code{header-line}, | |
2278 @code{horizontal-scroll-bar}, @code{menu-bar}, @code{mode-line}, | |
2279 @code{vertical-line}, and @code{vertical-scroll-bar}. You can define | |
2280 meanings for mouse clicks in special window parts by defining key | |
2281 sequences using these imaginary prefix keys. | |
2282 | |
2283 For example, if you call @code{read-key-sequence} and then click the | |
2284 mouse on the window's mode line, you get two events, like this: | |
2285 | |
2286 @example | |
2287 (read-key-sequence "Click on the mode line: ") | |
2288 @result{} [mode-line | |
2289 (mouse-1 | |
2290 (#<window 6 on NEWS> mode-line | |
2291 (40 . 63) 5959987))] | |
2292 @end example | |
2293 | |
2294 @defvar num-input-keys | |
2295 @c Emacs 19 feature | |
2296 This variable's value is the number of key sequences processed so far in | |
2297 this Emacs session. This includes key sequences read from the terminal | |
2298 and key sequences read from keyboard macros being executed. | |
2299 @end defvar | |
2300 | |
2301 @node Reading One Event | |
2302 @subsection Reading One Event | |
2303 @cindex reading a single event | |
2304 @cindex event, reading only one | |
2305 | |
2306 The lowest level functions for command input are those that read a | |
2307 single event. | |
2308 | |
2309 None of the three functions below suppresses quitting. | |
2310 | |
2311 @defun read-event &optional prompt inherit-input-method seconds | |
2312 This function reads and returns the next event of command input, waiting | |
2313 if necessary until an event is available. Events can come directly from | |
2314 the user or from a keyboard macro. | |
2315 | |
2316 If the optional argument @var{prompt} is non-@code{nil}, it should be a | |
2317 string to display in the echo area as a prompt. Otherwise, | |
2318 @code{read-event} does not display any message to indicate it is waiting | |
2319 for input; instead, it prompts by echoing: it displays descriptions of | |
2320 the events that led to or were read by the current command. @xref{The | |
2321 Echo Area}. | |
2322 | |
2323 If @var{inherit-input-method} is non-@code{nil}, then the current input | |
2324 method (if any) is employed to make it possible to enter a | |
2325 non-@acronym{ASCII} character. Otherwise, input method handling is disabled | |
2326 for reading this event. | |
2327 | |
2328 If @code{cursor-in-echo-area} is non-@code{nil}, then @code{read-event} | |
2329 moves the cursor temporarily to the echo area, to the end of any message | |
2330 displayed there. Otherwise @code{read-event} does not move the cursor. | |
2331 | |
2332 If @var{seconds} is non-@code{nil}, it should be a number specifying | |
2333 the maximum time to wait for input, in seconds. If no input arrives | |
2334 within that time, @code{read-event} stops waiting and returns | |
2335 @code{nil}. A floating-point value for @var{seconds} means to wait | |
2336 for a fractional number of seconds. Some systems support only a whole | |
2337 number of seconds; on these systems, @var{seconds} is rounded down. | |
2338 If @var{seconds} is @code{nil}, @code{read-event} waits as long as | |
2339 necessary for input to arrive. | |
2340 | |
2341 If @var{seconds} is @code{nil}, Emacs is considered idle while waiting | |
2342 for user input to arrive. Idle timers---those created with | |
2343 @code{run-with-idle-timer} (@pxref{Idle Timers})---can run during this | |
2344 period. However, if @var{seconds} is non-@code{nil}, the state of | |
2345 idleness remains unchanged. If Emacs is non-idle when | |
2346 @code{read-event} is called, it remains non-idle throughout the | |
2347 operation of @code{read-event}; if Emacs is idle (which can happen if | |
2348 the call happens inside an idle timer), it remains idle. | |
2349 | |
2350 If @code{read-event} gets an event that is defined as a help character, | |
2351 then in some cases @code{read-event} processes the event directly without | |
2352 returning. @xref{Help Functions}. Certain other events, called | |
2353 @dfn{special events}, are also processed directly within | |
2354 @code{read-event} (@pxref{Special Events}). | |
2355 | |
2356 Here is what happens if you call @code{read-event} and then press the | |
2357 right-arrow function key: | |
2358 | |
2359 @example | |
2360 @group | |
2361 (read-event) | |
2362 @result{} right | |
2363 @end group | |
2364 @end example | |
2365 @end defun | |
2366 | |
2367 @defun read-char &optional prompt inherit-input-method seconds | |
2368 This function reads and returns a character of command input. If the | |
2369 user generates an event which is not a character (i.e. a mouse click or | |
2370 function key event), @code{read-char} signals an error. The arguments | |
2371 work as in @code{read-event}. | |
2372 | |
2373 In the first example, the user types the character @kbd{1} (@acronym{ASCII} | |
2374 code 49). The second example shows a keyboard macro definition that | |
2375 calls @code{read-char} from the minibuffer using @code{eval-expression}. | |
2376 @code{read-char} reads the keyboard macro's very next character, which | |
2377 is @kbd{1}. Then @code{eval-expression} displays its return value in | |
2378 the echo area. | |
2379 | |
2380 @example | |
2381 @group | |
2382 (read-char) | |
2383 @result{} 49 | |
2384 @end group | |
2385 | |
2386 @group | |
2387 ;; @r{We assume here you use @kbd{M-:} to evaluate this.} | |
2388 (symbol-function 'foo) | |
2389 @result{} "^[:(read-char)^M1" | |
2390 @end group | |
2391 @group | |
2392 (execute-kbd-macro 'foo) | |
2393 @print{} 49 | |
2394 @result{} nil | |
2395 @end group | |
2396 @end example | |
2397 @end defun | |
2398 | |
2399 @defun read-char-exclusive &optional prompt inherit-input-method seconds | |
2400 This function reads and returns a character of command input. If the | |
2401 user generates an event which is not a character, | |
2402 @code{read-char-exclusive} ignores it and reads another event, until it | |
2403 gets a character. The arguments work as in @code{read-event}. | |
2404 @end defun | |
2405 | |
2406 @defvar num-nonmacro-input-events | |
2407 This variable holds the total number of input events received so far | |
2408 from the terminal---not counting those generated by keyboard macros. | |
2409 @end defvar | |
2410 | |
2411 @node Event Mod | |
2412 @subsection Modifying and Translating Input Events | |
2413 | |
2414 Emacs modifies every event it reads according to | |
2415 @code{extra-keyboard-modifiers}, then translates it through | |
2416 @code{keyboard-translate-table} (if applicable), before returning it | |
2417 from @code{read-event}. | |
2418 | |
2419 @c Emacs 19 feature | |
2420 @defvar extra-keyboard-modifiers | |
2421 This variable lets Lisp programs ``press'' the modifier keys on the | |
2422 keyboard. The value is a character. Only the modifiers of the | |
2423 character matter. Each time the user types a keyboard key, it is | |
2424 altered as if those modifier keys were held down. For instance, if | |
2425 you bind @code{extra-keyboard-modifiers} to @code{?\C-\M-a}, then all | |
2426 keyboard input characters typed during the scope of the binding will | |
2427 have the control and meta modifiers applied to them. The character | |
2428 @code{?\C-@@}, equivalent to the integer 0, does not count as a control | |
2429 character for this purpose, but as a character with no modifiers. | |
2430 Thus, setting @code{extra-keyboard-modifiers} to zero cancels any | |
2431 modification. | |
2432 | |
2433 When using a window system, the program can ``press'' any of the | |
2434 modifier keys in this way. Otherwise, only the @key{CTL} and @key{META} | |
2435 keys can be virtually pressed. | |
2436 | |
2437 Note that this variable applies only to events that really come from | |
2438 the keyboard, and has no effect on mouse events or any other events. | |
2439 @end defvar | |
2440 | |
2441 @defvar keyboard-translate-table | |
2442 This variable is the translate table for keyboard characters. It lets | |
2443 you reshuffle the keys on the keyboard without changing any command | |
2444 bindings. Its value is normally a char-table, or else @code{nil}. | |
2445 (It can also be a string or vector, but this is considered obsolete.) | |
2446 | |
2447 If @code{keyboard-translate-table} is a char-table | |
2448 (@pxref{Char-Tables}), then each character read from the keyboard is | |
2449 looked up in this char-table. If the value found there is | |
2450 non-@code{nil}, then it is used instead of the actual input character. | |
2451 | |
2452 Note that this translation is the first thing that happens to a | |
2453 character after it is read from the terminal. Record-keeping features | |
2454 such as @code{recent-keys} and dribble files record the characters after | |
2455 translation. | |
2456 | |
2457 Note also that this translation is done before the characters are | |
94331
6d85304f4f12
(translation-table-for-input): Mark as obsolete.
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
87649
diff
changeset
|
2458 supplied to input methods (@pxref{Input Methods}). |
84053 | 2459 @end defvar |
2460 | |
2461 @defun keyboard-translate from to | |
2462 This function modifies @code{keyboard-translate-table} to translate | |
2463 character code @var{from} into character code @var{to}. It creates | |
2464 the keyboard translate table if necessary. | |
2465 @end defun | |
2466 | |
2467 Here's an example of using the @code{keyboard-translate-table} to | |
2468 make @kbd{C-x}, @kbd{C-c} and @kbd{C-v} perform the cut, copy and paste | |
2469 operations: | |
2470 | |
2471 @example | |
2472 (keyboard-translate ?\C-x 'control-x) | |
2473 (keyboard-translate ?\C-c 'control-c) | |
2474 (keyboard-translate ?\C-v 'control-v) | |
2475 (global-set-key [control-x] 'kill-region) | |
2476 (global-set-key [control-c] 'kill-ring-save) | |
2477 (global-set-key [control-v] 'yank) | |
2478 @end example | |
2479 | |
2480 @noindent | |
2481 On a graphical terminal that supports extended @acronym{ASCII} input, | |
2482 you can still get the standard Emacs meanings of one of those | |
2483 characters by typing it with the shift key. That makes it a different | |
2484 character as far as keyboard translation is concerned, but it has the | |
2485 same usual meaning. | |
2486 | |
2487 @xref{Translation Keymaps}, for mechanisms that translate event sequences | |
2488 at the level of @code{read-key-sequence}. | |
2489 | |
2490 @node Invoking the Input Method | |
2491 @subsection Invoking the Input Method | |
2492 | |
2493 The event-reading functions invoke the current input method, if any | |
2494 (@pxref{Input Methods}). If the value of @code{input-method-function} | |
2495 is non-@code{nil}, it should be a function; when @code{read-event} reads | |
2496 a printing character (including @key{SPC}) with no modifier bits, it | |
2497 calls that function, passing the character as an argument. | |
2498 | |
2499 @defvar input-method-function | |
2500 If this is non-@code{nil}, its value specifies the current input method | |
2501 function. | |
2502 | |
2503 @strong{Warning:} don't bind this variable with @code{let}. It is often | |
2504 buffer-local, and if you bind it around reading input (which is exactly | |
2505 when you @emph{would} bind it), switching buffers asynchronously while | |
2506 Emacs is waiting will cause the value to be restored in the wrong | |
2507 buffer. | |
2508 @end defvar | |
2509 | |
2510 The input method function should return a list of events which should | |
2511 be used as input. (If the list is @code{nil}, that means there is no | |
2512 input, so @code{read-event} waits for another event.) These events are | |
2513 processed before the events in @code{unread-command-events} | |
2514 (@pxref{Event Input Misc}). Events | |
2515 returned by the input method function are not passed to the input method | |
2516 function again, even if they are printing characters with no modifier | |
2517 bits. | |
2518 | |
2519 If the input method function calls @code{read-event} or | |
2520 @code{read-key-sequence}, it should bind @code{input-method-function} to | |
2521 @code{nil} first, to prevent recursion. | |
2522 | |
2523 The input method function is not called when reading the second and | |
2524 subsequent events of a key sequence. Thus, these characters are not | |
2525 subject to input method processing. The input method function should | |
2526 test the values of @code{overriding-local-map} and | |
2527 @code{overriding-terminal-local-map}; if either of these variables is | |
2528 non-@code{nil}, the input method should put its argument into a list and | |
2529 return that list with no further processing. | |
2530 | |
2531 @node Quoted Character Input | |
2532 @subsection Quoted Character Input | |
2533 @cindex quoted character input | |
2534 | |
2535 You can use the function @code{read-quoted-char} to ask the user to | |
2536 specify a character, and allow the user to specify a control or meta | |
2537 character conveniently, either literally or as an octal character code. | |
2538 The command @code{quoted-insert} uses this function. | |
2539 | |
2540 @defun read-quoted-char &optional prompt | |
2541 @cindex octal character input | |
2542 @cindex control characters, reading | |
2543 @cindex nonprinting characters, reading | |
2544 This function is like @code{read-char}, except that if the first | |
2545 character read is an octal digit (0-7), it reads any number of octal | |
2546 digits (but stopping if a non-octal digit is found), and returns the | |
2547 character represented by that numeric character code. If the | |
2548 character that terminates the sequence of octal digits is @key{RET}, | |
2549 it is discarded. Any other terminating character is used as input | |
2550 after this function returns. | |
2551 | |
2552 Quitting is suppressed when the first character is read, so that the | |
2553 user can enter a @kbd{C-g}. @xref{Quitting}. | |
2554 | |
2555 If @var{prompt} is supplied, it specifies a string for prompting the | |
2556 user. The prompt string is always displayed in the echo area, followed | |
2557 by a single @samp{-}. | |
2558 | |
2559 In the following example, the user types in the octal number 177 (which | |
2560 is 127 in decimal). | |
2561 | |
2562 @example | |
2563 (read-quoted-char "What character") | |
2564 | |
2565 @group | |
2566 ---------- Echo Area ---------- | |
2567 What character @kbd{1 7 7}- | |
2568 ---------- Echo Area ---------- | |
2569 | |
2570 @result{} 127 | |
2571 @end group | |
2572 @end example | |
2573 @end defun | |
2574 | |
2575 @need 2000 | |
2576 @node Event Input Misc | |
2577 @subsection Miscellaneous Event Input Features | |
2578 | |
2579 This section describes how to ``peek ahead'' at events without using | |
2580 them up, how to check for pending input, and how to discard pending | |
2581 input. See also the function @code{read-passwd} (@pxref{Reading a | |
2582 Password}). | |
2583 | |
2584 @defvar unread-command-events | |
2585 @cindex next input | |
2586 @cindex peeking at input | |
2587 This variable holds a list of events waiting to be read as command | |
2588 input. The events are used in the order they appear in the list, and | |
2589 removed one by one as they are used. | |
2590 | |
2591 The variable is needed because in some cases a function reads an event | |
2592 and then decides not to use it. Storing the event in this variable | |
2593 causes it to be processed normally, by the command loop or by the | |
2594 functions to read command input. | |
2595 | |
2596 @cindex prefix argument unreading | |
2597 For example, the function that implements numeric prefix arguments reads | |
2598 any number of digits. When it finds a non-digit event, it must unread | |
2599 the event so that it can be read normally by the command loop. | |
2600 Likewise, incremental search uses this feature to unread events with no | |
2601 special meaning in a search, because these events should exit the search | |
2602 and then execute normally. | |
2603 | |
2604 The reliable and easy way to extract events from a key sequence so as to | |
2605 put them in @code{unread-command-events} is to use | |
2606 @code{listify-key-sequence} (@pxref{Strings of Events}). | |
2607 | |
2608 Normally you add events to the front of this list, so that the events | |
2609 most recently unread will be reread first. | |
2610 | |
2611 Events read from this list are not normally added to the current | |
2612 command's key sequence (as returned by e.g. @code{this-command-keys}), | |
2613 as the events will already have been added once as they were read for | |
2614 the first time. An element of the form @code{(@code{t} . @var{event})} | |
2615 forces @var{event} to be added to the current command's key sequence. | |
2616 @end defvar | |
2617 | |
2618 @defun listify-key-sequence key | |
2619 This function converts the string or vector @var{key} to a list of | |
2620 individual events, which you can put in @code{unread-command-events}. | |
2621 @end defun | |
2622 | |
2623 @defvar unread-command-char | |
2624 This variable holds a character to be read as command input. | |
2625 A value of -1 means ``empty.'' | |
2626 | |
2627 This variable is mostly obsolete now that you can use | |
2628 @code{unread-command-events} instead; it exists only to support programs | |
2629 written for Emacs versions 18 and earlier. | |
2630 @end defvar | |
2631 | |
2632 @defun input-pending-p | |
2633 @cindex waiting for command key input | |
2634 This function determines whether any command input is currently | |
2635 available to be read. It returns immediately, with value @code{t} if | |
2636 there is available input, @code{nil} otherwise. On rare occasions it | |
2637 may return @code{t} when no input is available. | |
2638 @end defun | |
2639 | |
2640 @defvar last-input-event | |
2641 @defvarx last-input-char | |
2642 This variable records the last terminal input event read, whether | |
2643 as part of a command or explicitly by a Lisp program. | |
2644 | |
2645 In the example below, the Lisp program reads the character @kbd{1}, | |
2646 @acronym{ASCII} code 49. It becomes the value of @code{last-input-event}, | |
2647 while @kbd{C-e} (we assume @kbd{C-x C-e} command is used to evaluate | |
2648 this expression) remains the value of @code{last-command-event}. | |
2649 | |
2650 @example | |
2651 @group | |
2652 (progn (print (read-char)) | |
2653 (print last-command-event) | |
2654 last-input-event) | |
2655 @print{} 49 | |
2656 @print{} 5 | |
2657 @result{} 49 | |
2658 @end group | |
2659 @end example | |
2660 | |
2661 The alias @code{last-input-char} exists for compatibility with | |
2662 Emacs version 18. | |
2663 @end defvar | |
2664 | |
2665 @defmac while-no-input body@dots{} | |
2666 This construct runs the @var{body} forms and returns the value of the | |
2667 last one---but only if no input arrives. If any input arrives during | |
2668 the execution of the @var{body} forms, it aborts them (working much | |
2669 like a quit). The @code{while-no-input} form returns @code{nil} if | |
2670 aborted by a real quit, and returns @code{t} if aborted by arrival of | |
2671 other input. | |
2672 | |
2673 If a part of @var{body} binds @code{inhibit-quit} to non-@code{nil}, | |
2674 arrival of input during those parts won't cause an abort until | |
2675 the end of that part. | |
2676 | |
2677 If you want to be able to distinguish all possible values computed | |
2678 by @var{body} from both kinds of abort conditions, write the code | |
2679 like this: | |
2680 | |
2681 @example | |
2682 (while-no-input | |
2683 (list | |
2684 (progn . @var{body}))) | |
2685 @end example | |
2686 @end defmac | |
2687 | |
2688 @defun discard-input | |
2689 @cindex flushing input | |
2690 @cindex discarding input | |
2691 @cindex keyboard macro, terminating | |
2692 This function discards the contents of the terminal input buffer and | |
2693 cancels any keyboard macro that might be in the process of definition. | |
2694 It returns @code{nil}. | |
2695 | |
2696 In the following example, the user may type a number of characters right | |
2697 after starting the evaluation of the form. After the @code{sleep-for} | |
2698 finishes sleeping, @code{discard-input} discards any characters typed | |
2699 during the sleep. | |
2700 | |
2701 @example | |
2702 (progn (sleep-for 2) | |
2703 (discard-input)) | |
2704 @result{} nil | |
2705 @end example | |
2706 @end defun | |
2707 | |
2708 @node Special Events | |
2709 @section Special Events | |
2710 | |
2711 @cindex special events | |
2712 Special events are handled at a very low level---as soon as they are | |
2713 read. The @code{read-event} function processes these events itself, and | |
2714 never returns them. Instead, it keeps waiting for the first event | |
2715 that is not special and returns that one. | |
2716 | |
2717 Events that are handled in this way do not echo, they are never grouped | |
2718 into key sequences, and they never appear in the value of | |
2719 @code{last-command-event} or @code{(this-command-keys)}. They do not | |
2720 discard a numeric argument, they cannot be unread with | |
2721 @code{unread-command-events}, they may not appear in a keyboard macro, | |
2722 and they are not recorded in a keyboard macro while you are defining | |
2723 one. | |
2724 | |
2725 These events do, however, appear in @code{last-input-event} immediately | |
2726 after they are read, and this is the way for the event's definition to | |
2727 find the actual event. | |
2728 | |
2729 The events types @code{iconify-frame}, @code{make-frame-visible}, | |
2730 @code{delete-frame}, @code{drag-n-drop}, and user signals like | |
2731 @code{sigusr1} are normally handled in this way. The keymap which | |
2732 defines how to handle special events---and which events are special---is | |
2733 in the variable @code{special-event-map} (@pxref{Active Keymaps}). | |
2734 | |
2735 @node Waiting | |
2736 @section Waiting for Elapsed Time or Input | |
2737 @cindex waiting | |
2738 | |
2739 The wait functions are designed to wait for a certain amount of time | |
2740 to pass or until there is input. For example, you may wish to pause in | |
2741 the middle of a computation to allow the user time to view the display. | |
2742 @code{sit-for} pauses and updates the screen, and returns immediately if | |
2743 input comes in, while @code{sleep-for} pauses without updating the | |
2744 screen. | |
2745 | |
2746 @defun sit-for seconds &optional nodisp | |
2747 This function performs redisplay (provided there is no pending input | |
2748 from the user), then waits @var{seconds} seconds, or until input is | |
2749 available. The usual purpose of @code{sit-for} is to give the user | |
2750 time to read text that you display. The value is @code{t} if | |
2751 @code{sit-for} waited the full time with no input arriving | |
2752 (@pxref{Event Input Misc}). Otherwise, the value is @code{nil}. | |
2753 | |
2754 The argument @var{seconds} need not be an integer. If it is a floating | |
2755 point number, @code{sit-for} waits for a fractional number of seconds. | |
2756 Some systems support only a whole number of seconds; on these systems, | |
2757 @var{seconds} is rounded down. | |
2758 | |
2759 The expression @code{(sit-for 0)} is equivalent to @code{(redisplay)}, | |
2760 i.e. it requests a redisplay, without any delay, if there is no pending input. | |
2761 @xref{Forcing Redisplay}. | |
2762 | |
2763 If @var{nodisp} is non-@code{nil}, then @code{sit-for} does not | |
2764 redisplay, but it still returns as soon as input is available (or when | |
2765 the timeout elapses). | |
2766 | |
2767 In batch mode (@pxref{Batch Mode}), @code{sit-for} cannot be | |
2768 interrupted, even by input from the standard input descriptor. It is | |
2769 thus equivalent to @code{sleep-for}, which is described below. | |
2770 | |
2771 It is also possible to call @code{sit-for} with three arguments, | |
2772 as @code{(sit-for @var{seconds} @var{millisec} @var{nodisp})}, | |
2773 but that is considered obsolete. | |
2774 @end defun | |
2775 | |
2776 @defun sleep-for seconds &optional millisec | |
2777 This function simply pauses for @var{seconds} seconds without updating | |
2778 the display. It pays no attention to available input. It returns | |
2779 @code{nil}. | |
2780 | |
2781 The argument @var{seconds} need not be an integer. If it is a floating | |
2782 point number, @code{sleep-for} waits for a fractional number of seconds. | |
2783 Some systems support only a whole number of seconds; on these systems, | |
2784 @var{seconds} is rounded down. | |
2785 | |
2786 The optional argument @var{millisec} specifies an additional waiting | |
2787 period measured in milliseconds. This adds to the period specified by | |
2788 @var{seconds}. If the system doesn't support waiting fractions of a | |
2789 second, you get an error if you specify nonzero @var{millisec}. | |
2790 | |
2791 Use @code{sleep-for} when you wish to guarantee a delay. | |
2792 @end defun | |
2793 | |
2794 @xref{Time of Day}, for functions to get the current time. | |
2795 | |
2796 @node Quitting | |
2797 @section Quitting | |
2798 @cindex @kbd{C-g} | |
2799 @cindex quitting | |
2800 @cindex interrupt Lisp functions | |
2801 | |
2802 Typing @kbd{C-g} while a Lisp function is running causes Emacs to | |
2803 @dfn{quit} whatever it is doing. This means that control returns to the | |
2804 innermost active command loop. | |
2805 | |
2806 Typing @kbd{C-g} while the command loop is waiting for keyboard input | |
2807 does not cause a quit; it acts as an ordinary input character. In the | |
2808 simplest case, you cannot tell the difference, because @kbd{C-g} | |
2809 normally runs the command @code{keyboard-quit}, whose effect is to quit. | |
2810 However, when @kbd{C-g} follows a prefix key, they combine to form an | |
2811 undefined key. The effect is to cancel the prefix key as well as any | |
2812 prefix argument. | |
2813 | |
2814 In the minibuffer, @kbd{C-g} has a different definition: it aborts out | |
2815 of the minibuffer. This means, in effect, that it exits the minibuffer | |
2816 and then quits. (Simply quitting would return to the command loop | |
2817 @emph{within} the minibuffer.) The reason why @kbd{C-g} does not quit | |
2818 directly when the command reader is reading input is so that its meaning | |
2819 can be redefined in the minibuffer in this way. @kbd{C-g} following a | |
2820 prefix key is not redefined in the minibuffer, and it has its normal | |
2821 effect of canceling the prefix key and prefix argument. This too | |
2822 would not be possible if @kbd{C-g} always quit directly. | |
2823 | |
2824 When @kbd{C-g} does directly quit, it does so by setting the variable | |
2825 @code{quit-flag} to @code{t}. Emacs checks this variable at appropriate | |
2826 times and quits if it is not @code{nil}. Setting @code{quit-flag} | |
2827 non-@code{nil} in any way thus causes a quit. | |
2828 | |
2829 At the level of C code, quitting cannot happen just anywhere; only at the | |
2830 special places that check @code{quit-flag}. The reason for this is | |
2831 that quitting at other places might leave an inconsistency in Emacs's | |
2832 internal state. Because quitting is delayed until a safe place, quitting | |
2833 cannot make Emacs crash. | |
2834 | |
2835 Certain functions such as @code{read-key-sequence} or | |
2836 @code{read-quoted-char} prevent quitting entirely even though they wait | |
2837 for input. Instead of quitting, @kbd{C-g} serves as the requested | |
2838 input. In the case of @code{read-key-sequence}, this serves to bring | |
2839 about the special behavior of @kbd{C-g} in the command loop. In the | |
2840 case of @code{read-quoted-char}, this is so that @kbd{C-q} can be used | |
2841 to quote a @kbd{C-g}. | |
2842 | |
2843 @cindex preventing quitting | |
2844 You can prevent quitting for a portion of a Lisp function by binding | |
2845 the variable @code{inhibit-quit} to a non-@code{nil} value. Then, | |
2846 although @kbd{C-g} still sets @code{quit-flag} to @code{t} as usual, the | |
2847 usual result of this---a quit---is prevented. Eventually, | |
2848 @code{inhibit-quit} will become @code{nil} again, such as when its | |
2849 binding is unwound at the end of a @code{let} form. At that time, if | |
2850 @code{quit-flag} is still non-@code{nil}, the requested quit happens | |
2851 immediately. This behavior is ideal when you wish to make sure that | |
2852 quitting does not happen within a ``critical section'' of the program. | |
2853 | |
2854 @cindex @code{read-quoted-char} quitting | |
2855 In some functions (such as @code{read-quoted-char}), @kbd{C-g} is | |
2856 handled in a special way that does not involve quitting. This is done | |
2857 by reading the input with @code{inhibit-quit} bound to @code{t}, and | |
2858 setting @code{quit-flag} to @code{nil} before @code{inhibit-quit} | |
2859 becomes @code{nil} again. This excerpt from the definition of | |
2860 @code{read-quoted-char} shows how this is done; it also shows that | |
2861 normal quitting is permitted after the first character of input. | |
2862 | |
2863 @example | |
2864 (defun read-quoted-char (&optional prompt) | |
2865 "@dots{}@var{documentation}@dots{}" | |
2866 (let ((message-log-max nil) done (first t) (code 0) char) | |
2867 (while (not done) | |
2868 (let ((inhibit-quit first) | |
2869 @dots{}) | |
2870 (and prompt (message "%s-" prompt)) | |
2871 (setq char (read-event)) | |
2872 (if inhibit-quit (setq quit-flag nil))) | |
2873 @r{@dots{}set the variable @code{code}@dots{}}) | |
2874 code)) | |
2875 @end example | |
2876 | |
2877 @defvar quit-flag | |
2878 If this variable is non-@code{nil}, then Emacs quits immediately, unless | |
2879 @code{inhibit-quit} is non-@code{nil}. Typing @kbd{C-g} ordinarily sets | |
2880 @code{quit-flag} non-@code{nil}, regardless of @code{inhibit-quit}. | |
2881 @end defvar | |
2882 | |
2883 @defvar inhibit-quit | |
2884 This variable determines whether Emacs should quit when @code{quit-flag} | |
2885 is set to a value other than @code{nil}. If @code{inhibit-quit} is | |
2886 non-@code{nil}, then @code{quit-flag} has no special effect. | |
2887 @end defvar | |
2888 | |
2889 @defmac with-local-quit body@dots{} | |
2890 This macro executes @var{body} forms in sequence, but allows quitting, at | |
2891 least locally, within @var{body} even if @code{inhibit-quit} was | |
2892 non-@code{nil} outside this construct. It returns the value of the | |
2893 last form in @var{body}, unless exited by quitting, in which case | |
2894 it returns @code{nil}. | |
2895 | |
2896 If @code{inhibit-quit} is @code{nil} on entry to @code{with-local-quit}, | |
2897 it only executes the @var{body}, and setting @code{quit-flag} causes | |
2898 a normal quit. However, if @code{inhibit-quit} is non-@code{nil} so | |
2899 that ordinary quitting is delayed, a non-@code{nil} @code{quit-flag} | |
2900 triggers a special kind of local quit. This ends the execution of | |
2901 @var{body} and exits the @code{with-local-quit} body with | |
2902 @code{quit-flag} still non-@code{nil}, so that another (ordinary) quit | |
2903 will happen as soon as that is allowed. If @code{quit-flag} is | |
2904 already non-@code{nil} at the beginning of @var{body}, the local quit | |
2905 happens immediately and the body doesn't execute at all. | |
2906 | |
2907 This macro is mainly useful in functions that can be called from | |
2908 timers, process filters, process sentinels, @code{pre-command-hook}, | |
2909 @code{post-command-hook}, and other places where @code{inhibit-quit} is | |
2910 normally bound to @code{t}. | |
2911 @end defmac | |
2912 | |
2913 @deffn Command keyboard-quit | |
2914 This function signals the @code{quit} condition with @code{(signal 'quit | |
2915 nil)}. This is the same thing that quitting does. (See @code{signal} | |
2916 in @ref{Errors}.) | |
2917 @end deffn | |
2918 | |
2919 You can specify a character other than @kbd{C-g} to use for quitting. | |
2920 See the function @code{set-input-mode} in @ref{Terminal Input}. | |
2921 | |
2922 @node Prefix Command Arguments | |
2923 @section Prefix Command Arguments | |
2924 @cindex prefix argument | |
2925 @cindex raw prefix argument | |
2926 @cindex numeric prefix argument | |
2927 | |
2928 Most Emacs commands can use a @dfn{prefix argument}, a number | |
2929 specified before the command itself. (Don't confuse prefix arguments | |
2930 with prefix keys.) The prefix argument is at all times represented by a | |
2931 value, which may be @code{nil}, meaning there is currently no prefix | |
2932 argument. Each command may use the prefix argument or ignore it. | |
2933 | |
2934 There are two representations of the prefix argument: @dfn{raw} and | |
2935 @dfn{numeric}. The editor command loop uses the raw representation | |
2936 internally, and so do the Lisp variables that store the information, but | |
2937 commands can request either representation. | |
2938 | |
2939 Here are the possible values of a raw prefix argument: | |
2940 | |
2941 @itemize @bullet | |
2942 @item | |
2943 @code{nil}, meaning there is no prefix argument. Its numeric value is | |
2944 1, but numerous commands make a distinction between @code{nil} and the | |
2945 integer 1. | |
2946 | |
2947 @item | |
2948 An integer, which stands for itself. | |
2949 | |
2950 @item | |
2951 A list of one element, which is an integer. This form of prefix | |
2952 argument results from one or a succession of @kbd{C-u}'s with no | |
2953 digits. The numeric value is the integer in the list, but some | |
2954 commands make a distinction between such a list and an integer alone. | |
2955 | |
2956 @item | |
2957 The symbol @code{-}. This indicates that @kbd{M--} or @kbd{C-u -} was | |
2958 typed, without following digits. The equivalent numeric value is | |
2959 @minus{}1, but some commands make a distinction between the integer | |
2960 @minus{}1 and the symbol @code{-}. | |
2961 @end itemize | |
2962 | |
2963 We illustrate these possibilities by calling the following function with | |
2964 various prefixes: | |
2965 | |
2966 @example | |
2967 @group | |
2968 (defun display-prefix (arg) | |
2969 "Display the value of the raw prefix arg." | |
2970 (interactive "P") | |
2971 (message "%s" arg)) | |
2972 @end group | |
2973 @end example | |
2974 | |
2975 @noindent | |
2976 Here are the results of calling @code{display-prefix} with various | |
2977 raw prefix arguments: | |
2978 | |
2979 @example | |
2980 M-x display-prefix @print{} nil | |
2981 | |
2982 C-u M-x display-prefix @print{} (4) | |
2983 | |
2984 C-u C-u M-x display-prefix @print{} (16) | |
2985 | |
2986 C-u 3 M-x display-prefix @print{} 3 | |
2987 | |
2988 M-3 M-x display-prefix @print{} 3 ; @r{(Same as @code{C-u 3}.)} | |
2989 | |
2990 C-u - M-x display-prefix @print{} - | |
2991 | |
2992 M-- M-x display-prefix @print{} - ; @r{(Same as @code{C-u -}.)} | |
2993 | |
2994 C-u - 7 M-x display-prefix @print{} -7 | |
2995 | |
2996 M-- 7 M-x display-prefix @print{} -7 ; @r{(Same as @code{C-u -7}.)} | |
2997 @end example | |
2998 | |
2999 Emacs uses two variables to store the prefix argument: | |
3000 @code{prefix-arg} and @code{current-prefix-arg}. Commands such as | |
3001 @code{universal-argument} that set up prefix arguments for other | |
3002 commands store them in @code{prefix-arg}. In contrast, | |
3003 @code{current-prefix-arg} conveys the prefix argument to the current | |
3004 command, so setting it has no effect on the prefix arguments for future | |
3005 commands. | |
3006 | |
3007 Normally, commands specify which representation to use for the prefix | |
3008 argument, either numeric or raw, in the @code{interactive} specification. | |
3009 (@xref{Using Interactive}.) Alternatively, functions may look at the | |
3010 value of the prefix argument directly in the variable | |
3011 @code{current-prefix-arg}, but this is less clean. | |
3012 | |
3013 @defun prefix-numeric-value arg | |
3014 This function returns the numeric meaning of a valid raw prefix argument | |
3015 value, @var{arg}. The argument may be a symbol, a number, or a list. | |
3016 If it is @code{nil}, the value 1 is returned; if it is @code{-}, the | |
3017 value @minus{}1 is returned; if it is a number, that number is returned; | |
3018 if it is a list, the @sc{car} of that list (which should be a number) is | |
3019 returned. | |
3020 @end defun | |
3021 | |
3022 @defvar current-prefix-arg | |
3023 This variable holds the raw prefix argument for the @emph{current} | |
3024 command. Commands may examine it directly, but the usual method for | |
3025 accessing it is with @code{(interactive "P")}. | |
3026 @end defvar | |
3027 | |
3028 @defvar prefix-arg | |
3029 The value of this variable is the raw prefix argument for the | |
3030 @emph{next} editing command. Commands such as @code{universal-argument} | |
3031 that specify prefix arguments for the following command work by setting | |
3032 this variable. | |
3033 @end defvar | |
3034 | |
3035 @defvar last-prefix-arg | |
3036 The raw prefix argument value used by the previous command. | |
3037 @end defvar | |
3038 | |
3039 The following commands exist to set up prefix arguments for the | |
3040 following command. Do not call them for any other reason. | |
3041 | |
3042 @deffn Command universal-argument | |
3043 This command reads input and specifies a prefix argument for the | |
3044 following command. Don't call this command yourself unless you know | |
3045 what you are doing. | |
3046 @end deffn | |
3047 | |
3048 @deffn Command digit-argument arg | |
3049 This command adds to the prefix argument for the following command. The | |
3050 argument @var{arg} is the raw prefix argument as it was before this | |
3051 command; it is used to compute the updated prefix argument. Don't call | |
3052 this command yourself unless you know what you are doing. | |
3053 @end deffn | |
3054 | |
3055 @deffn Command negative-argument arg | |
3056 This command adds to the numeric argument for the next command. The | |
3057 argument @var{arg} is the raw prefix argument as it was before this | |
3058 command; its value is negated to form the new prefix argument. Don't | |
3059 call this command yourself unless you know what you are doing. | |
3060 @end deffn | |
3061 | |
3062 @node Recursive Editing | |
3063 @section Recursive Editing | |
3064 @cindex recursive command loop | |
3065 @cindex recursive editing level | |
3066 @cindex command loop, recursive | |
3067 | |
3068 The Emacs command loop is entered automatically when Emacs starts up. | |
3069 This top-level invocation of the command loop never exits; it keeps | |
3070 running as long as Emacs does. Lisp programs can also invoke the | |
3071 command loop. Since this makes more than one activation of the command | |
3072 loop, we call it @dfn{recursive editing}. A recursive editing level has | |
3073 the effect of suspending whatever command invoked it and permitting the | |
3074 user to do arbitrary editing before resuming that command. | |
3075 | |
3076 The commands available during recursive editing are the same ones | |
3077 available in the top-level editing loop and defined in the keymaps. | |
3078 Only a few special commands exit the recursive editing level; the others | |
3079 return to the recursive editing level when they finish. (The special | |
3080 commands for exiting are always available, but they do nothing when | |
3081 recursive editing is not in progress.) | |
3082 | |
3083 All command loops, including recursive ones, set up all-purpose error | |
3084 handlers so that an error in a command run from the command loop will | |
3085 not exit the loop. | |
3086 | |
3087 @cindex minibuffer input | |
3088 Minibuffer input is a special kind of recursive editing. It has a few | |
3089 special wrinkles, such as enabling display of the minibuffer and the | |
3090 minibuffer window, but fewer than you might suppose. Certain keys | |
3091 behave differently in the minibuffer, but that is only because of the | |
3092 minibuffer's local map; if you switch windows, you get the usual Emacs | |
3093 commands. | |
3094 | |
3095 @cindex @code{throw} example | |
3096 @kindex exit | |
3097 @cindex exit recursive editing | |
3098 @cindex aborting | |
3099 To invoke a recursive editing level, call the function | |
3100 @code{recursive-edit}. This function contains the command loop; it also | |
3101 contains a call to @code{catch} with tag @code{exit}, which makes it | |
3102 possible to exit the recursive editing level by throwing to @code{exit} | |
3103 (@pxref{Catch and Throw}). If you throw a value other than @code{t}, | |
3104 then @code{recursive-edit} returns normally to the function that called | |
3105 it. The command @kbd{C-M-c} (@code{exit-recursive-edit}) does this. | |
3106 Throwing a @code{t} value causes @code{recursive-edit} to quit, so that | |
3107 control returns to the command loop one level up. This is called | |
3108 @dfn{aborting}, and is done by @kbd{C-]} (@code{abort-recursive-edit}). | |
3109 | |
3110 Most applications should not use recursive editing, except as part of | |
3111 using the minibuffer. Usually it is more convenient for the user if you | |
3112 change the major mode of the current buffer temporarily to a special | |
3113 major mode, which should have a command to go back to the previous mode. | |
3114 (The @kbd{e} command in Rmail uses this technique.) Or, if you wish to | |
3115 give the user different text to edit ``recursively,'' create and select | |
3116 a new buffer in a special mode. In this mode, define a command to | |
3117 complete the processing and go back to the previous buffer. (The | |
3118 @kbd{m} command in Rmail does this.) | |
3119 | |
3120 Recursive edits are useful in debugging. You can insert a call to | |
3121 @code{debug} into a function definition as a sort of breakpoint, so that | |
3122 you can look around when the function gets there. @code{debug} invokes | |
3123 a recursive edit but also provides the other features of the debugger. | |
3124 | |
3125 Recursive editing levels are also used when you type @kbd{C-r} in | |
3126 @code{query-replace} or use @kbd{C-x q} (@code{kbd-macro-query}). | |
3127 | |
3128 @defun recursive-edit | |
3129 @cindex suspend evaluation | |
3130 This function invokes the editor command loop. It is called | |
3131 automatically by the initialization of Emacs, to let the user begin | |
3132 editing. When called from a Lisp program, it enters a recursive editing | |
3133 level. | |
3134 | |
3135 If the current buffer is not the same as the selected window's buffer, | |
3136 @code{recursive-edit} saves and restores the current buffer. Otherwise, | |
3137 if you switch buffers, the buffer you switched to is current after | |
3138 @code{recursive-edit} returns. | |
3139 | |
3140 In the following example, the function @code{simple-rec} first | |
3141 advances point one word, then enters a recursive edit, printing out a | |
3142 message in the echo area. The user can then do any editing desired, and | |
3143 then type @kbd{C-M-c} to exit and continue executing @code{simple-rec}. | |
3144 | |
3145 @example | |
3146 (defun simple-rec () | |
3147 (forward-word 1) | |
3148 (message "Recursive edit in progress") | |
3149 (recursive-edit) | |
3150 (forward-word 1)) | |
3151 @result{} simple-rec | |
3152 (simple-rec) | |
3153 @result{} nil | |
3154 @end example | |
3155 @end defun | |
3156 | |
3157 @deffn Command exit-recursive-edit | |
3158 This function exits from the innermost recursive edit (including | |
3159 minibuffer input). Its definition is effectively @code{(throw 'exit | |
3160 nil)}. | |
3161 @end deffn | |
3162 | |
3163 @deffn Command abort-recursive-edit | |
3164 This function aborts the command that requested the innermost recursive | |
3165 edit (including minibuffer input), by signaling @code{quit} | |
3166 after exiting the recursive edit. Its definition is effectively | |
3167 @code{(throw 'exit t)}. @xref{Quitting}. | |
3168 @end deffn | |
3169 | |
3170 @deffn Command top-level | |
3171 This function exits all recursive editing levels; it does not return a | |
3172 value, as it jumps completely out of any computation directly back to | |
3173 the main command loop. | |
3174 @end deffn | |
3175 | |
3176 @defun recursion-depth | |
3177 This function returns the current depth of recursive edits. When no | |
3178 recursive edit is active, it returns 0. | |
3179 @end defun | |
3180 | |
3181 @node Disabling Commands | |
3182 @section Disabling Commands | |
3183 @cindex disabled command | |
3184 | |
3185 @dfn{Disabling a command} marks the command as requiring user | |
3186 confirmation before it can be executed. Disabling is used for commands | |
3187 which might be confusing to beginning users, to prevent them from using | |
3188 the commands by accident. | |
3189 | |
3190 @kindex disabled | |
3191 The low-level mechanism for disabling a command is to put a | |
3192 non-@code{nil} @code{disabled} property on the Lisp symbol for the | |
3193 command. These properties are normally set up by the user's | |
3194 init file (@pxref{Init File}) with Lisp expressions such as this: | |
3195 | |
3196 @example | |
3197 (put 'upcase-region 'disabled t) | |
3198 @end example | |
3199 | |
3200 @noindent | |
3201 For a few commands, these properties are present by default (you can | |
3202 remove them in your init file if you wish). | |
3203 | |
3204 If the value of the @code{disabled} property is a string, the message | |
3205 saying the command is disabled includes that string. For example: | |
3206 | |
3207 @example | |
3208 (put 'delete-region 'disabled | |
3209 "Text deleted this way cannot be yanked back!\n") | |
3210 @end example | |
3211 | |
3212 @xref{Disabling,,, emacs, The GNU Emacs Manual}, for the details on | |
3213 what happens when a disabled command is invoked interactively. | |
3214 Disabling a command has no effect on calling it as a function from Lisp | |
3215 programs. | |
3216 | |
3217 @deffn Command enable-command command | |
3218 Allow @var{command} (a symbol) to be executed without special | |
3219 confirmation from now on, and alter the user's init file (@pxref{Init | |
3220 File}) so that this will apply to future sessions. | |
3221 @end deffn | |
3222 | |
3223 @deffn Command disable-command command | |
3224 Require special confirmation to execute @var{command} from now on, and | |
3225 alter the user's init file so that this will apply to future sessions. | |
3226 @end deffn | |
3227 | |
3228 @defvar disabled-command-function | |
3229 The value of this variable should be a function. When the user | |
3230 invokes a disabled command interactively, this function is called | |
3231 instead of the disabled command. It can use @code{this-command-keys} | |
3232 to determine what the user typed to run the command, and thus find the | |
3233 command itself. | |
3234 | |
3235 The value may also be @code{nil}. Then all commands work normally, | |
3236 even disabled ones. | |
3237 | |
3238 By default, the value is a function that asks the user whether to | |
3239 proceed. | |
3240 @end defvar | |
3241 | |
3242 @node Command History | |
3243 @section Command History | |
3244 @cindex command history | |
3245 @cindex complex command | |
3246 @cindex history of commands | |
3247 | |
3248 The command loop keeps a history of the complex commands that have | |
3249 been executed, to make it convenient to repeat these commands. A | |
3250 @dfn{complex command} is one for which the interactive argument reading | |
3251 uses the minibuffer. This includes any @kbd{M-x} command, any | |
3252 @kbd{M-:} command, and any command whose @code{interactive} | |
3253 specification reads an argument from the minibuffer. Explicit use of | |
3254 the minibuffer during the execution of the command itself does not cause | |
3255 the command to be considered complex. | |
3256 | |
3257 @defvar command-history | |
3258 This variable's value is a list of recent complex commands, each | |
3259 represented as a form to evaluate. It continues to accumulate all | |
3260 complex commands for the duration of the editing session, but when it | |
3261 reaches the maximum size (@pxref{Minibuffer History}), the oldest | |
3262 elements are deleted as new ones are added. | |
3263 | |
3264 @example | |
3265 @group | |
3266 command-history | |
3267 @result{} ((switch-to-buffer "chistory.texi") | |
3268 (describe-key "^X^[") | |
3269 (visit-tags-table "~/emacs/src/") | |
3270 (find-tag "repeat-complex-command")) | |
3271 @end group | |
3272 @end example | |
3273 @end defvar | |
3274 | |
3275 This history list is actually a special case of minibuffer history | |
3276 (@pxref{Minibuffer History}), with one special twist: the elements are | |
3277 expressions rather than strings. | |
3278 | |
3279 There are a number of commands devoted to the editing and recall of | |
3280 previous commands. The commands @code{repeat-complex-command}, and | |
3281 @code{list-command-history} are described in the user manual | |
3282 (@pxref{Repetition,,, emacs, The GNU Emacs Manual}). Within the | |
3283 minibuffer, the usual minibuffer history commands are available. | |
3284 | |
3285 @node Keyboard Macros | |
3286 @section Keyboard Macros | |
3287 @cindex keyboard macros | |
3288 | |
3289 A @dfn{keyboard macro} is a canned sequence of input events that can | |
3290 be considered a command and made the definition of a key. The Lisp | |
3291 representation of a keyboard macro is a string or vector containing the | |
3292 events. Don't confuse keyboard macros with Lisp macros | |
3293 (@pxref{Macros}). | |
3294 | |
3295 @defun execute-kbd-macro kbdmacro &optional count loopfunc | |
3296 This function executes @var{kbdmacro} as a sequence of events. If | |
3297 @var{kbdmacro} is a string or vector, then the events in it are executed | |
3298 exactly as if they had been input by the user. The sequence is | |
3299 @emph{not} expected to be a single key sequence; normally a keyboard | |
3300 macro definition consists of several key sequences concatenated. | |
3301 | |
3302 If @var{kbdmacro} is a symbol, then its function definition is used in | |
3303 place of @var{kbdmacro}. If that is another symbol, this process repeats. | |
3304 Eventually the result should be a string or vector. If the result is | |
3305 not a symbol, string, or vector, an error is signaled. | |
3306 | |
3307 The argument @var{count} is a repeat count; @var{kbdmacro} is executed that | |
3308 many times. If @var{count} is omitted or @code{nil}, @var{kbdmacro} is | |
3309 executed once. If it is 0, @var{kbdmacro} is executed over and over until it | |
3310 encounters an error or a failing search. | |
3311 | |
3312 If @var{loopfunc} is non-@code{nil}, it is a function that is called, | |
3313 without arguments, prior to each iteration of the macro. If | |
3314 @var{loopfunc} returns @code{nil}, then this stops execution of the macro. | |
3315 | |
3316 @xref{Reading One Event}, for an example of using @code{execute-kbd-macro}. | |
3317 @end defun | |
3318 | |
3319 @defvar executing-kbd-macro | |
3320 This variable contains the string or vector that defines the keyboard | |
3321 macro that is currently executing. It is @code{nil} if no macro is | |
3322 currently executing. A command can test this variable so as to behave | |
3323 differently when run from an executing macro. Do not set this variable | |
3324 yourself. | |
3325 @end defvar | |
3326 | |
3327 @defvar defining-kbd-macro | |
3328 This variable is non-@code{nil} if and only if a keyboard macro is | |
3329 being defined. A command can test this variable so as to behave | |
3330 differently while a macro is being defined. The value is | |
3331 @code{append} while appending to the definition of an existing macro. | |
3332 The commands @code{start-kbd-macro}, @code{kmacro-start-macro} and | |
3333 @code{end-kbd-macro} set this variable---do not set it yourself. | |
3334 | |
3335 The variable is always local to the current terminal and cannot be | |
3336 buffer-local. @xref{Multiple Displays}. | |
3337 @end defvar | |
3338 | |
3339 @defvar last-kbd-macro | |
3340 This variable is the definition of the most recently defined keyboard | |
3341 macro. Its value is a string or vector, or @code{nil}. | |
3342 | |
3343 The variable is always local to the current terminal and cannot be | |
3344 buffer-local. @xref{Multiple Displays}. | |
3345 @end defvar | |
3346 | |
3347 @defvar kbd-macro-termination-hook | |
3348 This normal hook (@pxref{Standard Hooks}) is run when a keyboard | |
3349 macro terminates, regardless of what caused it to terminate (reaching | |
3350 the macro end or an error which ended the macro prematurely). | |
3351 @end defvar | |
3352 | |
3353 @ignore | |
3354 arch-tag: e34944ad-7d5c-4980-be00-36a5fe54d4b1 | |
3355 @end ignore |