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