Mercurial > emacs
annotate lispref/commands.texi @ 23096:e4419c63d4d7
(message-send-mail-with-sendmail): Bind
coding-system-for-write by the return value of
select-message-coding-system.
(message-send-mail-with-qmail): Likewise.
author | Kenichi Handa <handa@m17n.org> |
---|---|
date | Tue, 25 Aug 1998 10:25:03 +0000 |
parents | 63f6e25f0cbd |
children | 0d84817a4973 |
rev | line source |
---|---|
6260 | 1 @c -*-texinfo-*- |
2 @c This is part of the GNU Emacs Lisp Reference Manual. | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998 Free Software Foundation, Inc. |
6260 | 4 @c See the file elisp.texi for copying conditions. |
5 @setfilename ../info/commands | |
6 @node Command Loop, Keymaps, Minibuffers, Top | |
7 @chapter Command Loop | |
8 @cindex editor command loop | |
9 @cindex command loop | |
10 | |
11 When you run Emacs, it enters the @dfn{editor command loop} almost | |
12 immediately. This loop reads key sequences, executes their definitions, | |
13 and displays the results. In this chapter, we describe how these things | |
14 are done, and the subroutines that allow Lisp programs to do them. | |
15 | |
16 @menu | |
17 * Command Overview:: How the command loop reads commands. | |
18 * Defining Commands:: Specifying how a function should read arguments. | |
19 * Interactive Call:: Calling a command, so that it will read arguments. | |
20 * Command Loop Info:: Variables set by the command loop for you to examine. | |
21 * Input Events:: What input looks like when you read it. | |
22 * Reading Input:: How to read input events from the keyboard or mouse. | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
23 * Special Events:: Events processed immediately and individually. |
6260 | 24 * Waiting:: Waiting for user input or elapsed time. |
25 * Quitting:: How @kbd{C-g} works. How to catch or defer quitting. | |
26 * Prefix Command Arguments:: How the commands to set prefix args work. | |
27 * Recursive Editing:: Entering a recursive edit, | |
28 and why you usually shouldn't. | |
29 * Disabling Commands:: How the command loop handles disabled commands. | |
30 * Command History:: How the command history is set up, and how accessed. | |
31 * Keyboard Macros:: How keyboard macros are implemented. | |
32 @end menu | |
33 | |
34 @node Command Overview | |
35 @section Command Loop Overview | |
36 | |
37 The first thing the command loop must do is read a key sequence, which | |
38 is a sequence of events that translates into a command. It does this by | |
39 calling the function @code{read-key-sequence}. Your Lisp code can also | |
40 call this function (@pxref{Key Sequence Input}). Lisp programs can also | |
41 do input at a lower level with @code{read-event} (@pxref{Reading One | |
42 Event}) or discard pending input with @code{discard-input} | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
43 (@pxref{Event Input Misc}). |
6260 | 44 |
45 The key sequence is translated into a command through the currently | |
46 active keymaps. @xref{Key Lookup}, for information on how this is done. | |
47 The result should be a keyboard macro or an interactively callable | |
48 function. If the key is @kbd{M-x}, then it reads the name of another | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
49 command, which it then calls. This is done by the command |
6260 | 50 @code{execute-extended-command} (@pxref{Interactive Call}). |
51 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
52 To execute a command requires first reading the arguments for it. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
53 This is done by calling @code{command-execute} (@pxref{Interactive |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
54 Call}). For commands written in Lisp, the @code{interactive} |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
55 specification says how to read the arguments. This may use the prefix |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
56 argument (@pxref{Prefix Command Arguments}) or may read with prompting |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
57 in the minibuffer (@pxref{Minibuffers}). For example, the command |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
58 @code{find-file} has an @code{interactive} specification which says to |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
59 read a file name using the minibuffer. The command's function body does |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
60 not use the minibuffer; if you call this command from Lisp code as a |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
61 function, you must supply the file name string as an ordinary Lisp |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
62 function argument. |
6260 | 63 |
64 If the command is a string or vector (i.e., a keyboard macro) then | |
65 @code{execute-kbd-macro} is used to execute it. You can call this | |
66 function yourself (@pxref{Keyboard Macros}). | |
67 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
68 To terminate the execution of a running command, type @kbd{C-g}. This |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
69 character causes @dfn{quitting} (@pxref{Quitting}). |
6260 | 70 |
71 @defvar pre-command-hook | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
72 The editor command loop runs this normal hook before each command. At |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
73 that time, @code{this-command} contains the command that is about to |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
74 run, and @code{last-command} describes the previous command. |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
75 @xref{Hooks}. |
6260 | 76 @end defvar |
77 | |
78 @defvar post-command-hook | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
79 The editor command loop runs this normal hook after each command |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
80 (including commands terminated prematurely by quitting or by errors), |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
81 and also when the command loop is first entered. At that time, |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
82 @code{this-command} describes the command that just ran, and |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
83 @code{last-command} describes the command before that. @xref{Hooks}. |
6260 | 84 @end defvar |
85 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
86 Quitting is suppressed while running @code{pre-command-hook} and |
12098 | 87 @code{post-command-hook}. If an error happens while executing one of |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
88 these hooks, it terminates execution of the hook, and clears the hook |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
89 variable to @code{nil} so as to prevent an infinite loop of errors. |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
90 |
6260 | 91 @node Defining Commands |
92 @section Defining Commands | |
93 @cindex defining commands | |
94 @cindex commands, defining | |
95 @cindex functions, making them interactive | |
96 @cindex interactive function | |
97 | |
98 A Lisp function becomes a command when its body contains, at top | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
99 level, a form that calls the special form @code{interactive}. This |
6260 | 100 form does nothing when actually executed, but its presence serves as a |
101 flag to indicate that interactive calling is permitted. Its argument | |
102 controls the reading of arguments for an interactive call. | |
103 | |
104 @menu | |
105 * Using Interactive:: General rules for @code{interactive}. | |
106 * Interactive Codes:: The standard letter-codes for reading arguments | |
107 in various ways. | |
108 * Interactive Examples:: Examples of how to read interactive arguments. | |
109 @end menu | |
110 | |
111 @node Using Interactive | |
112 @subsection Using @code{interactive} | |
113 | |
114 This section describes how to write the @code{interactive} form that | |
115 makes a Lisp function an interactively-callable command. | |
116 | |
117 @defspec interactive arg-descriptor | |
118 @cindex argument descriptors | |
119 This special form declares that the function in which it appears is a | |
120 command, and that it may therefore be called interactively (via | |
121 @kbd{M-x} or by entering a key sequence bound to it). The argument | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
122 @var{arg-descriptor} declares how to compute the arguments to the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
123 command when the command is called interactively. |
6260 | 124 |
125 A command may be called from Lisp programs like any other function, but | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
126 then the caller supplies the arguments and @var{arg-descriptor} has no |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
127 effect. |
6260 | 128 |
129 The @code{interactive} form has its effect because the command loop | |
130 (actually, its subroutine @code{call-interactively}) scans through the | |
131 function definition looking for it, before calling the function. Once | |
132 the function is called, all its body forms including the | |
133 @code{interactive} form are executed, but at this time | |
134 @code{interactive} simply returns @code{nil} without even evaluating its | |
135 argument. | |
136 @end defspec | |
137 | |
138 There are three possibilities for the argument @var{arg-descriptor}: | |
139 | |
140 @itemize @bullet | |
141 @item | |
142 It may be omitted or @code{nil}; then the command is called with no | |
143 arguments. This leads quickly to an error if the command requires one | |
144 or more arguments. | |
145 | |
146 @item | |
147 It may be a Lisp expression that is not a string; then it should be a | |
148 form that is evaluated to get a list of arguments to pass to the | |
149 command. | |
150 @cindex argument evaluation form | |
151 | |
10834
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
152 If this expression reads keyboard input (this includes using the |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
153 minibuffer), keep in mind that the integer value of point or the mark |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
154 before reading input may be incorrect after reading input. This is |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
155 because the current buffer may be receiving subprocess output; |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
156 if subprocess output arrives while the command is waiting for input, |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
157 it could relocate point and the mark. |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
158 |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
159 Here's an example of what @emph{not} to do: |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
160 |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
161 @smallexample |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
162 (interactive |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
163 (list (region-beginning) (region-end) |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
164 (read-string "Foo: " nil 'my-history))) |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
165 @end smallexample |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
166 |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
167 @noindent |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
168 Here's how to avoid the problem, by examining point and the mark only |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
169 after reading the keyboard input: |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
170 |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
171 @smallexample |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
172 (interactive |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
173 (let ((string (read-string "Foo: " nil 'my-history))) |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
174 (list (region-beginning) (region-end) string))) |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
175 @end smallexample |
e79e5c9e7722
Warn that interactive should get point and mark only after minibuffer input.
Richard M. Stallman <rms@gnu.org>
parents:
8532
diff
changeset
|
176 |
6260 | 177 @item |
178 @cindex argument prompt | |
179 It may be a string; then its contents should consist of a code character | |
180 followed by a prompt (which some code characters use and some ignore). | |
181 The prompt ends either with the end of the string or with a newline. | |
182 Here is a simple example: | |
183 | |
184 @smallexample | |
185 (interactive "bFrobnicate buffer: ") | |
186 @end smallexample | |
187 | |
188 @noindent | |
189 The code letter @samp{b} says to read the name of an existing buffer, | |
190 with completion. The buffer name is the sole argument passed to the | |
191 command. The rest of the string is a prompt. | |
192 | |
193 If there is a newline character in the string, it terminates the prompt. | |
194 If the string does not end there, then the rest of the string should | |
195 contain another code character and prompt, specifying another argument. | |
196 You can specify any number of arguments in this way. | |
197 | |
198 @c Emacs 19 feature | |
199 The prompt string can use @samp{%} to include previous argument values | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
200 (starting with the first argument) in the prompt. This is done using |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
201 @code{format} (@pxref{Formatting Strings}). For example, here is how |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
202 you could read the name of an existing buffer followed by a new name to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
203 give to that buffer: |
6260 | 204 |
205 @smallexample | |
206 @group | |
207 (interactive "bBuffer to rename: \nsRename buffer %s to: ") | |
208 @end group | |
209 @end smallexample | |
210 | |
211 @cindex @samp{*} in interactive | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
212 @cindex read-only buffers in interactive |
6260 | 213 If the first character in the string is @samp{*}, then an error is |
214 signaled if the buffer is read-only. | |
215 | |
216 @cindex @samp{@@} in interactive | |
217 @c Emacs 19 feature | |
218 If the first character in the string is @samp{@@}, and if the key | |
219 sequence used to invoke the command includes any mouse events, then | |
220 the window associated with the first of those events is selected | |
221 before the command is run. | |
222 | |
223 You can use @samp{*} and @samp{@@} together; the order does not matter. | |
224 Actual reading of arguments is controlled by the rest of the prompt | |
225 string (starting with the first character that is not @samp{*} or | |
226 @samp{@@}). | |
227 @end itemize | |
228 | |
229 @node Interactive Codes | |
230 @comment node-name, next, previous, up | |
231 @subsection Code Characters for @code{interactive} | |
232 @cindex interactive code description | |
233 @cindex description for interactive codes | |
234 @cindex codes, interactive, description of | |
235 @cindex characters for interactive codes | |
236 | |
237 The code character descriptions below contain a number of key words, | |
238 defined here as follows: | |
239 | |
240 @table @b | |
241 @item Completion | |
242 @cindex interactive completion | |
243 Provide completion. @key{TAB}, @key{SPC}, and @key{RET} perform name | |
244 completion because the argument is read using @code{completing-read} | |
245 (@pxref{Completion}). @kbd{?} displays a list of possible completions. | |
246 | |
247 @item Existing | |
248 Require the name of an existing object. An invalid name is not | |
249 accepted; the commands to exit the minibuffer do not exit if the current | |
250 input is not valid. | |
251 | |
252 @item Default | |
253 @cindex default argument string | |
254 A default value of some sort is used if the user enters no text in the | |
255 minibuffer. The default depends on the code character. | |
256 | |
257 @item No I/O | |
258 This code letter computes an argument without reading any input. | |
259 Therefore, it does not use a prompt string, and any prompt string you | |
260 supply is ignored. | |
261 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
262 Even though the code letter doesn't use a prompt string, you must follow |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
263 it with a newline if it is not the last code character in the string. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
264 |
6260 | 265 @item Prompt |
266 A prompt immediately follows the code character. The prompt ends either | |
267 with the end of the string or with a newline. | |
268 | |
269 @item Special | |
270 This code character is meaningful only at the beginning of the | |
271 interactive string, and it does not look for a prompt or a newline. | |
272 It is a single, isolated character. | |
273 @end table | |
274 | |
275 @cindex reading interactive arguments | |
276 Here are the code character descriptions for use with @code{interactive}: | |
277 | |
278 @table @samp | |
279 @item * | |
280 Signal an error if the current buffer is read-only. Special. | |
281 | |
282 @item @@ | |
283 Select the window mentioned in the first mouse event in the key | |
284 sequence that invoked this command. Special. | |
285 | |
286 @item a | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
287 A function name (i.e., a symbol satisfying @code{fboundp}). Existing, |
6260 | 288 Completion, Prompt. |
289 | |
290 @item b | |
291 The name of an existing buffer. By default, uses the name of the | |
292 current buffer (@pxref{Buffers}). Existing, Completion, Default, | |
293 Prompt. | |
294 | |
295 @item B | |
296 A buffer name. The buffer need not exist. By default, uses the name of | |
297 a recently used buffer other than the current buffer. Completion, | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
298 Default, Prompt. |
6260 | 299 |
300 @item c | |
301 A character. The cursor does not move into the echo area. Prompt. | |
302 | |
303 @item C | |
304 A command name (i.e., a symbol satisfying @code{commandp}). Existing, | |
305 Completion, Prompt. | |
306 | |
307 @item d | |
308 @cindex position argument | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
309 The position of point, as an integer (@pxref{Point}). No I/O. |
6260 | 310 |
311 @item D | |
312 A directory name. The default is the current default directory of the | |
313 current buffer, @code{default-directory} (@pxref{System Environment}). | |
314 Existing, Completion, Default, Prompt. | |
315 | |
316 @item e | |
317 The first or next mouse event in the key sequence that invoked the command. | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
318 More precisely, @samp{e} gets events that are lists, so you can look at |
6260 | 319 the data in the lists. @xref{Input Events}. No I/O. |
320 | |
321 You can use @samp{e} more than once in a single command's interactive | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
322 specification. If the key sequence that invoked the command has |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
323 @var{n} events that are lists, the @var{n}th @samp{e} provides the |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
324 @var{n}th such event. Events that are not lists, such as function keys |
6260 | 325 and @sc{ASCII} characters, do not count where @samp{e} is concerned. |
326 | |
327 @item f | |
328 A file name of an existing file (@pxref{File Names}). The default | |
329 directory is @code{default-directory}. Existing, Completion, Default, | |
330 Prompt. | |
331 | |
332 @item F | |
333 A file name. The file need not exist. Completion, Default, Prompt. | |
334 | |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
335 @item i |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
336 An irrelevant argument. This code always supplies @code{nil} as |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
337 the argument's value. No I/O. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
338 |
6260 | 339 @item k |
340 A key sequence (@pxref{Keymap Terminology}). This keeps reading events | |
341 until a command (or undefined command) is found in the current key | |
342 maps. The key sequence argument is represented as a string or vector. | |
343 The cursor does not move into the echo area. Prompt. | |
344 | |
345 This kind of input is used by commands such as @code{describe-key} and | |
346 @code{global-set-key}. | |
347 | |
12067 | 348 @item K |
349 A key sequence, whose definition you intend to change. This works like | |
350 @samp{k}, except that it suppresses, for the last input event in the key | |
351 sequence, the conversions that are normally used (when necessary) to | |
352 convert an undefined key into a defined one. | |
353 | |
6260 | 354 @item m |
355 @cindex marker argument | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
356 The position of the mark, as an integer. No I/O. |
6260 | 357 |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
358 @item M |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
359 Arbitrary text, read in the minibuffer using the current buffer's input |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
360 method, and returned as a string (@pxref{Input Methods,,, emacs, The GNU |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
361 Emacs Manual}). Prompt. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
362 |
6260 | 363 @item n |
364 A number read with the minibuffer. If the input is not a number, the | |
365 user is asked to try again. The prefix argument, if any, is not used. | |
366 Prompt. | |
367 | |
368 @item N | |
369 @cindex raw prefix argument usage | |
13853
7c317c94b1f6
Changed interactive spec N.
Richard M. Stallman <rms@gnu.org>
parents:
13007
diff
changeset
|
370 The numeric prefix argument; but if there is no prefix argument, read a |
7c317c94b1f6
Changed interactive spec N.
Richard M. Stallman <rms@gnu.org>
parents:
13007
diff
changeset
|
371 number as with @kbd{n}. Requires a number. @xref{Prefix Command |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
372 Arguments}. Prompt. |
6260 | 373 |
374 @item p | |
375 @cindex numeric prefix argument usage | |
376 The numeric prefix argument. (Note that this @samp{p} is lower case.) | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
377 No I/O. |
6260 | 378 |
379 @item P | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
380 The raw prefix argument. (Note that this @samp{P} is upper case.) No |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
381 I/O. |
6260 | 382 |
383 @item r | |
384 @cindex region argument | |
385 Point and the mark, as two numeric arguments, smallest first. This is | |
386 the only code letter that specifies two successive arguments rather than | |
387 one. No I/O. | |
388 | |
389 @item s | |
390 Arbitrary text, read in the minibuffer and returned as a string | |
391 (@pxref{Text from Minibuffer}). Terminate the input with either | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
392 @kbd{C-j} or @key{RET}. (@kbd{C-q} may be used to include either of |
6260 | 393 these characters in the input.) Prompt. |
394 | |
395 @item S | |
396 An interned symbol whose name is read in the minibuffer. Any whitespace | |
397 character terminates the input. (Use @kbd{C-q} to include whitespace in | |
398 the string.) Other characters that normally terminate a symbol (e.g., | |
399 parentheses and brackets) do not do so here. Prompt. | |
400 | |
401 @item v | |
402 A variable declared to be a user option (i.e., satisfying the predicate | |
403 @code{user-variable-p}). @xref{High-Level Completion}. Existing, | |
404 Completion, Prompt. | |
405 | |
406 @item x | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
407 A Lisp object, specified with its read syntax, terminated with a |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
408 @kbd{C-j} or @key{RET}. The object is not evaluated. @xref{Object from |
6260 | 409 Minibuffer}. Prompt. |
410 | |
411 @item X | |
412 @cindex evaluated expression argument | |
413 A Lisp form is read as with @kbd{x}, but then evaluated so that its | |
414 value becomes the argument for the command. Prompt. | |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
415 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
416 @item z |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
417 A coding system name (a symbol). If the user enters null input, the |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
418 argument value is @code{nil}. @xref{Coding Systems}. Completion, |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
419 Existing, Prompt. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
420 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
421 @item Z |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
422 A coding system name (a symbol)---but only if this command has a prefix |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
423 argument. With no prefix argument, @samp{Z} provides @code{nil} as the |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
424 argument value. Completion, Existing, Prompt. |
6260 | 425 @end table |
426 | |
427 @node Interactive Examples | |
428 @comment node-name, next, previous, up | |
429 @subsection Examples of Using @code{interactive} | |
430 @cindex examples of using @code{interactive} | |
431 @cindex @code{interactive}, examples of using | |
432 | |
433 Here are some examples of @code{interactive}: | |
434 | |
435 @example | |
436 @group | |
437 (defun foo1 () ; @r{@code{foo1} takes no arguments,} | |
438 (interactive) ; @r{just moves forward two words.} | |
439 (forward-word 2)) | |
440 @result{} foo1 | |
441 @end group | |
442 | |
443 @group | |
444 (defun foo2 (n) ; @r{@code{foo2} takes one argument,} | |
445 (interactive "p") ; @r{which is the numeric prefix.} | |
446 (forward-word (* 2 n))) | |
447 @result{} foo2 | |
448 @end group | |
449 | |
450 @group | |
451 (defun foo3 (n) ; @r{@code{foo3} takes one argument,} | |
452 (interactive "nCount:") ; @r{which is read with the Minibuffer.} | |
453 (forward-word (* 2 n))) | |
454 @result{} foo3 | |
455 @end group | |
456 | |
457 @group | |
458 (defun three-b (b1 b2 b3) | |
459 "Select three existing buffers. | |
460 Put them into three windows, selecting the last one." | |
461 @end group | |
462 (interactive "bBuffer1:\nbBuffer2:\nbBuffer3:") | |
463 (delete-other-windows) | |
464 (split-window (selected-window) 8) | |
465 (switch-to-buffer b1) | |
466 (other-window 1) | |
467 (split-window (selected-window) 8) | |
468 (switch-to-buffer b2) | |
469 (other-window 1) | |
470 (switch-to-buffer b3)) | |
471 @result{} three-b | |
472 @group | |
473 (three-b "*scratch*" "declarations.texi" "*mail*") | |
474 @result{} nil | |
475 @end group | |
476 @end example | |
477 | |
478 @node Interactive Call | |
479 @section Interactive Call | |
480 @cindex interactive call | |
481 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
482 After the command loop has translated a key sequence into a command it |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
483 invokes that command using the function @code{command-execute}. If the |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
484 command is a function, @code{command-execute} calls |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
485 @code{call-interactively}, which reads the arguments and calls the |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
486 command. You can also call these functions yourself. |
6260 | 487 |
488 @defun commandp object | |
489 Returns @code{t} if @var{object} is suitable for calling interactively; | |
490 that is, if @var{object} is a command. Otherwise, returns @code{nil}. | |
491 | |
492 The interactively callable objects include strings and vectors (treated | |
493 as keyboard macros), lambda expressions that contain a top-level call to | |
12098 | 494 @code{interactive}, byte-code function objects made from such lambda |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
495 expressions, autoload objects that are declared as interactive |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
496 (non-@code{nil} fourth argument to @code{autoload}), and some of the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
497 primitive functions. |
6260 | 498 |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
499 A symbol satisfies @code{commandp} if its function definition satisfies |
6260 | 500 @code{commandp}. |
501 | |
502 Keys and keymaps are not commands. Rather, they are used to look up | |
503 commands (@pxref{Keymaps}). | |
504 | |
505 See @code{documentation} in @ref{Accessing Documentation}, for a | |
506 realistic example of using @code{commandp}. | |
507 @end defun | |
508 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
509 @defun call-interactively command &optional record-flag keys |
6260 | 510 This function calls the interactively callable function @var{command}, |
511 reading arguments according to its interactive calling specifications. | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
512 An error is signaled if @var{command} is not a function or if it cannot |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
513 be called interactively (i.e., is not a command). Note that keyboard |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
514 macros (strings and vectors) are not accepted, even though they are |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
515 considered commands, because they are not functions. |
6260 | 516 |
517 @cindex record command history | |
518 If @var{record-flag} is non-@code{nil}, then this command and its | |
519 arguments are unconditionally added to the list @code{command-history}. | |
520 Otherwise, the command is added only if it uses the minibuffer to read | |
521 an argument. @xref{Command History}. | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
522 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
523 The argument @var{keys}, if given, specifies the sequence of events to |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
524 supply if the command inquires which events were used to invoke it. |
6260 | 525 @end defun |
526 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
527 @defun command-execute command &optional record-flag keys |
6260 | 528 @cindex keyboard macro execution |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
529 This function executes @var{command}. The argument @var{command} must |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
530 satisfy the @code{commandp} predicate; i.e., it must be an interactively |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
531 callable function or a keyboard macro. |
6260 | 532 |
533 A string or vector as @var{command} is executed with | |
534 @code{execute-kbd-macro}. A function is passed to | |
535 @code{call-interactively}, along with the optional @var{record-flag}. | |
536 | |
537 A symbol is handled by using its function definition in its place. A | |
538 symbol with an @code{autoload} definition counts as a command if it was | |
539 declared to stand for an interactively callable function. Such a | |
540 definition is handled by loading the specified library and then | |
541 rechecking the definition of the symbol. | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
542 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
543 The argument @var{keys}, if given, specifies the sequence of events to |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
544 supply if the command inquires which events were used to invoke it. |
6260 | 545 @end defun |
546 | |
547 @deffn Command execute-extended-command prefix-argument | |
548 @cindex read command name | |
549 This function reads a command name from the minibuffer using | |
550 @code{completing-read} (@pxref{Completion}). Then it uses | |
551 @code{command-execute} to call the specified command. Whatever that | |
552 command returns becomes the value of @code{execute-extended-command}. | |
553 | |
554 @cindex execute with prefix argument | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
555 If the command asks for a prefix argument, it receives the value |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
556 @var{prefix-argument}. If @code{execute-extended-command} is called |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
557 interactively, the current raw prefix argument is used for |
6260 | 558 @var{prefix-argument}, and thus passed on to whatever command is run. |
559 | |
560 @c !!! Should this be @kindex? | |
561 @cindex @kbd{M-x} | |
562 @code{execute-extended-command} is the normal definition of @kbd{M-x}, | |
563 so it uses the string @w{@samp{M-x }} as a prompt. (It would be better | |
564 to take the prompt from the events used to invoke | |
565 @code{execute-extended-command}, but that is painful to implement.) A | |
566 description of the value of the prefix argument, if any, also becomes | |
567 part of the prompt. | |
568 | |
569 @example | |
570 @group | |
571 (execute-extended-command 1) | |
572 ---------- Buffer: Minibuffer ---------- | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
573 1 M-x forward-word RET |
6260 | 574 ---------- Buffer: Minibuffer ---------- |
575 @result{} t | |
576 @end group | |
577 @end example | |
578 @end deffn | |
579 | |
580 @defun interactive-p | |
16736
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
581 This function returns @code{t} if the containing function (the one whose |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
582 code includes the call to @code{interactive-p}) was called |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
583 interactively, with the function @code{call-interactively}. (It makes |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
584 no difference whether @code{call-interactively} was called from Lisp or |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
585 directly from the editor command loop.) If the containing function was |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
586 called by Lisp evaluation (or with @code{apply} or @code{funcall}), then |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
587 it was not called interactively. |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
588 @end defun |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
589 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
590 The most common use of @code{interactive-p} is for deciding whether to |
6260 | 591 print an informative message. As a special exception, |
592 @code{interactive-p} returns @code{nil} whenever a keyboard macro is | |
593 being run. This is to suppress the informative messages and speed | |
594 execution of the macro. | |
595 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
596 For example: |
6260 | 597 |
598 @example | |
599 @group | |
600 (defun foo () | |
601 (interactive) | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
602 (when (interactive-p) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
603 (message "foo"))) |
6260 | 604 @result{} foo |
605 @end group | |
606 | |
607 @group | |
608 (defun bar () | |
609 (interactive) | |
610 (setq foobar (list (foo) (interactive-p)))) | |
611 @result{} bar | |
612 @end group | |
613 | |
614 @group | |
615 ;; @r{Type @kbd{M-x foo}.} | |
616 @print{} foo | |
617 @end group | |
618 | |
619 @group | |
620 ;; @r{Type @kbd{M-x bar}.} | |
621 ;; @r{This does not print anything.} | |
622 @end group | |
623 | |
624 @group | |
625 foobar | |
626 @result{} (nil t) | |
627 @end group | |
628 @end example | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
629 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
630 The other way to do this sort of job is to make the command take an |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
631 argument @code{print-message} which should be non-@code{nil} in an |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
632 interactive call, and use the @code{interactive} spec to make sure it is |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
633 non-@code{nil}. Here's how: |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
634 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
635 @example |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
636 (defun foo (&optional print-message) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
637 (interactive "p") |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
638 (when print-message |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
639 (message "foo"))) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
640 @end example |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
641 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
642 The numeric prefix argument, provided by @samp{p}, is never @code{nil}. |
6260 | 643 |
644 @node Command Loop Info | |
645 @comment node-name, next, previous, up | |
646 @section Information from the Command Loop | |
647 | |
648 The editor command loop sets several Lisp variables to keep status | |
649 records for itself and for commands that are run. | |
650 | |
651 @defvar last-command | |
652 This variable records the name of the previous command executed by the | |
653 command loop (the one before the current command). Normally the value | |
654 is a symbol with a function definition, but this is not guaranteed. | |
655 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
656 The value is copied from @code{this-command} when a command returns to |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
657 the command loop, except when the command has specified a prefix |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
658 argument for the following command. |
12098 | 659 |
660 This variable is always local to the current terminal and cannot be | |
661 buffer-local. @xref{Multiple Displays}. | |
6260 | 662 @end defvar |
663 | |
22440
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
664 @tindex real-last-command |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
665 @defvar real-last-command |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
666 This variable is set up by Emacs just like @code{last-command}, |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
667 but never altered by Lisp programs. |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
668 @end defvar |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
669 |
6260 | 670 @defvar this-command |
671 @cindex current command | |
672 This variable records the name of the command now being executed by | |
673 the editor command loop. Like @code{last-command}, it is normally a symbol | |
674 with a function definition. | |
675 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
676 The command loop sets this variable just before running a command, and |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
677 copies its value into @code{last-command} when the command finishes |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
678 (unless the command specified a prefix argument for the following |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
679 command). |
6260 | 680 |
681 @cindex kill command repetition | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
682 Some commands set this variable during their execution, as a flag for |
12098 | 683 whatever command runs next. In particular, the functions for killing text |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
684 set @code{this-command} to @code{kill-region} so that any kill commands |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
685 immediately following will know to append the killed text to the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
686 previous kill. |
6260 | 687 @end defvar |
688 | |
689 If you do not want a particular command to be recognized as the previous | |
690 command in the case where it got an error, you must code that command to | |
691 prevent this. One way is to set @code{this-command} to @code{t} at the | |
692 beginning of the command, and set @code{this-command} back to its proper | |
693 value at the end, like this: | |
694 | |
695 @example | |
696 (defun foo (args@dots{}) | |
697 (interactive @dots{}) | |
698 (let ((old-this-command this-command)) | |
699 (setq this-command t) | |
700 @r{@dots{}do the work@dots{}} | |
701 (setq this-command old-this-command))) | |
702 @end example | |
703 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
704 @noindent |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
705 We do not bind @code{this-command} with @code{let} because that would |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
706 restore the old value in case of error---a feature of @code{let} which |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
707 in this case does precisely what we want to avoid. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
708 |
6260 | 709 @defun this-command-keys |
710 This function returns a string or vector containing the key sequence | |
711 that invoked the present command, plus any previous commands that | |
712 generated the prefix argument for this command. The value is a string | |
713 if all those events were characters. @xref{Input Events}. | |
714 | |
715 @example | |
716 @group | |
717 (this-command-keys) | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
718 ;; @r{Now use @kbd{C-u C-x C-e} to evaluate that.} |
6260 | 719 @result{} "^U^X^E" |
720 @end group | |
721 @end example | |
722 @end defun | |
723 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
724 @defun this-command-keys-vector |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
725 Like @code{this-command-keys}, except that it always returns |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
726 the events in a vector, so you do never need to deal with the complexities |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
727 of storing input events in a string (@pxref{Strings of Events}). |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
728 @end defun |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
729 |
6260 | 730 @defvar last-nonmenu-event |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
731 This variable holds the last input event read as part of a key sequence, |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
732 not counting events resulting from mouse menus. |
6260 | 733 |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
734 One use of this variable is for telling @code{x-popup-menu} where to pop |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
735 up a menu. It is also used internally by @code{y-or-n-p} |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
736 (@pxref{Yes-or-No Queries}). |
6260 | 737 @end defvar |
738 | |
739 @defvar last-command-event | |
740 @defvarx last-command-char | |
741 This variable is set to the last input event that was read by the | |
742 command loop as part of a command. The principal use of this variable | |
743 is in @code{self-insert-command}, which uses it to decide which | |
744 character to insert. | |
745 | |
746 @example | |
747 @group | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
748 last-command-event |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
749 ;; @r{Now use @kbd{C-u C-x C-e} to evaluate that.} |
6260 | 750 @result{} 5 |
751 @end group | |
752 @end example | |
753 | |
754 @noindent | |
755 The value is 5 because that is the @sc{ASCII} code for @kbd{C-e}. | |
756 | |
757 The alias @code{last-command-char} exists for compatibility with | |
758 Emacs version 18. | |
759 @end defvar | |
760 | |
761 @c Emacs 19 feature | |
762 @defvar last-event-frame | |
763 This variable records which frame the last input event was directed to. | |
764 Usually this is the frame that was selected when the event was | |
765 generated, but if that frame has redirected input focus to another | |
766 frame, the value is the frame to which the event was redirected. | |
767 @xref{Input Focus}. | |
768 @end defvar | |
769 | |
770 @node Input Events | |
771 @section Input Events | |
772 @cindex events | |
773 @cindex input events | |
774 | |
775 The Emacs command loop reads a sequence of @dfn{input events} that | |
776 represent keyboard or mouse activity. The events for keyboard activity | |
777 are characters or symbols; mouse events are always lists. This section | |
778 describes the representation and meaning of input events in detail. | |
779 | |
780 @defun eventp object | |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
781 This function returns non-@code{nil} if @var{object} is an input event |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
782 or event type. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
783 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
784 Note that any symbol might be used as an event or an event type. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
785 @code{eventp} cannot distinguish whether a symbol is intended by Lisp |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
786 code to be used as an event. Instead, it distinguishes whether the |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
787 symbol has actually been used in an event that has been read as input in |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
788 the current Emacs session. If a symbol has not yet been so used, |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
789 @code{eventp} returns @code{nil}. |
6260 | 790 @end defun |
791 | |
792 @menu | |
793 * Keyboard Events:: Ordinary characters--keys with symbols on them. | |
794 * Function Keys:: Function keys--keys with names, not symbols. | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
795 * Mouse Events:: Overview of mouse events. |
6260 | 796 * Click Events:: Pushing and releasing a mouse button. |
797 * Drag Events:: Moving the mouse before releasing the button. | |
798 * Button-Down Events:: A button was pushed and not yet released. | |
799 * Repeat Events:: Double and triple click (or drag, or down). | |
800 * Motion Events:: Just moving the mouse, not pushing a button. | |
801 * Focus Events:: Moving the mouse between frames. | |
12067 | 802 * Misc Events:: Other events window systems can generate. |
6260 | 803 * Event Examples:: Examples of the lists for mouse events. |
804 * Classifying Events:: Finding the modifier keys in an event symbol. | |
805 Event types. | |
806 * Accessing Events:: Functions to extract info from events. | |
807 * Strings of Events:: Special considerations for putting | |
808 keyboard character events in a string. | |
809 @end menu | |
810 | |
811 @node Keyboard Events | |
812 @subsection Keyboard Events | |
813 | |
814 There are two kinds of input you can get from the keyboard: ordinary | |
815 keys, and function keys. Ordinary keys correspond to characters; the | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
816 events they generate are represented in Lisp as characters. The event |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
817 type of a character event is the character itself (an integer); see |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
818 @ref{Classifying Events}. |
6260 | 819 |
820 @cindex modifier bits (of input character) | |
821 @cindex basic code (of input character) | |
822 An input character event consists of a @dfn{basic code} between 0 and | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
823 524287, plus any or all of these @dfn{modifier bits}: |
6260 | 824 |
825 @table @asis | |
826 @item meta | |
12098 | 827 The |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
828 @tex |
12098 | 829 $2^{27}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
830 @end tex |
12098 | 831 @ifinfo |
832 2**27 | |
833 @end ifinfo | |
834 bit in the character code indicates a character | |
6260 | 835 typed with the meta key held down. |
836 | |
837 @item control | |
12098 | 838 The |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
839 @tex |
12098 | 840 $2^{26}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
841 @end tex |
12098 | 842 @ifinfo |
843 2**26 | |
844 @end ifinfo | |
845 bit in the character code indicates a non-@sc{ASCII} | |
6260 | 846 control character. |
847 | |
848 @sc{ASCII} control characters such as @kbd{C-a} have special basic | |
849 codes of their own, so Emacs needs no special bit to indicate them. | |
850 Thus, the code for @kbd{C-a} is just 1. | |
851 | |
852 But if you type a control combination not in @sc{ASCII}, such as | |
853 @kbd{%} with the control key, the numeric value you get is the code | |
12098 | 854 for @kbd{%} plus |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
855 @tex |
12098 | 856 $2^{26}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
857 @end tex |
12098 | 858 @ifinfo |
859 2**26 | |
860 @end ifinfo | |
861 (assuming the terminal supports non-@sc{ASCII} | |
6260 | 862 control characters). |
863 | |
864 @item shift | |
12098 | 865 The |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
866 @tex |
12098 | 867 $2^{25}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
868 @end tex |
12098 | 869 @ifinfo |
870 2**25 | |
871 @end ifinfo | |
872 bit in the character code indicates an @sc{ASCII} control | |
6260 | 873 character typed with the shift key held down. |
874 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
875 For letters, the basic code itself indicates upper versus lower case; |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
876 for digits and punctuation, the shift key selects an entirely different |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
877 character with a different basic code. In order to keep within the |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
878 @sc{ASCII} character set whenever possible, Emacs avoids using the |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
879 @tex |
12098 | 880 $2^{25}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
881 @end tex |
12098 | 882 @ifinfo |
883 2**25 | |
884 @end ifinfo | |
885 bit for those characters. | |
6260 | 886 |
887 However, @sc{ASCII} provides no way to distinguish @kbd{C-A} from | |
12098 | 888 @kbd{C-a}, so Emacs uses the |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
889 @tex |
12098 | 890 $2^{25}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
891 @end tex |
12098 | 892 @ifinfo |
893 2**25 | |
894 @end ifinfo | |
895 bit in @kbd{C-A} and not in | |
6260 | 896 @kbd{C-a}. |
897 | |
898 @item hyper | |
12098 | 899 The |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
900 @tex |
12098 | 901 $2^{24}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
902 @end tex |
12098 | 903 @ifinfo |
904 2**24 | |
905 @end ifinfo | |
906 bit in the character code indicates a character | |
6260 | 907 typed with the hyper key held down. |
908 | |
909 @item super | |
12098 | 910 The |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
911 @tex |
12098 | 912 $2^{23}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
913 @end tex |
12098 | 914 @ifinfo |
915 2**23 | |
916 @end ifinfo | |
917 bit in the character code indicates a character | |
6260 | 918 typed with the super key held down. |
919 | |
920 @item alt | |
12098 | 921 The |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
922 @tex |
12098 | 923 $2^{22}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
924 @end tex |
12098 | 925 @ifinfo |
926 2**22 | |
927 @end ifinfo | |
928 bit in the character code indicates a character typed with | |
6260 | 929 the alt key held down. (On some terminals, the key labeled @key{ALT} |
930 is actually the meta key.) | |
931 @end table | |
932 | |
12098 | 933 It is best to avoid mentioning specific bit numbers in your program. |
934 To test the modifier bits of a character, use the function | |
935 @code{event-modifiers} (@pxref{Classifying Events}). When making key | |
936 bindings, you can use the read syntax for characters with modifier bits | |
937 (@samp{\C-}, @samp{\M-}, and so on). For making key bindings with | |
938 @code{define-key}, you can use lists such as @code{(control hyper ?x)} to | |
939 specify the characters (@pxref{Changing Key Bindings}). The function | |
940 @code{event-convert-list} converts such a list into an event type | |
941 (@pxref{Classifying Events}). | |
6260 | 942 |
943 @node Function Keys | |
944 @subsection Function Keys | |
945 | |
946 @cindex function keys | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
947 Most keyboards also have @dfn{function keys}---keys that have names or |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
948 symbols that are not characters. Function keys are represented in Emacs |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
949 Lisp as symbols; the symbol's name is the function key's label, in lower |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
950 case. For example, pressing a key labeled @key{F1} places the symbol |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
951 @code{f1} in the input stream. |
6260 | 952 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
953 The event type of a function key event is the event symbol itself. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
954 @xref{Classifying Events}. |
6260 | 955 |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
956 Here are a few special cases in the symbol-naming convention for |
6260 | 957 function keys: |
958 | |
959 @table @asis | |
960 @item @code{backspace}, @code{tab}, @code{newline}, @code{return}, @code{delete} | |
961 These keys correspond to common @sc{ASCII} control characters that have | |
962 special keys on most keyboards. | |
963 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
964 In @sc{ASCII}, @kbd{C-i} and @key{TAB} are the same character. If the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
965 terminal can distinguish between them, Emacs conveys the distinction to |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
966 Lisp programs by representing the former as the integer 9, and the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
967 latter as the symbol @code{tab}. |
6260 | 968 |
969 Most of the time, it's not useful to distinguish the two. So normally | |
15764 | 970 @code{function-key-map} (@pxref{Translating Input}) is set up to map |
971 @code{tab} into 9. Thus, a key binding for character code 9 (the | |
972 character @kbd{C-i}) also applies to @code{tab}. Likewise for the other | |
973 symbols in this group. The function @code{read-char} likewise converts | |
974 these events into characters. | |
6260 | 975 |
976 In @sc{ASCII}, @key{BS} is really @kbd{C-h}. But @code{backspace} | |
977 converts into the character code 127 (@key{DEL}), not into code 8 | |
978 (@key{BS}). This is what most users prefer. | |
979 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
980 @item @code{left}, @code{up}, @code{right}, @code{down} |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
981 Cursor arrow keys |
6260 | 982 @item @code{kp-add}, @code{kp-decimal}, @code{kp-divide}, @dots{} |
983 Keypad keys (to the right of the regular keyboard). | |
984 @item @code{kp-0}, @code{kp-1}, @dots{} | |
985 Keypad keys with digits. | |
986 @item @code{kp-f1}, @code{kp-f2}, @code{kp-f3}, @code{kp-f4} | |
987 Keypad PF keys. | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
988 @item @code{kp-home}, @code{kp-left}, @code{kp-up}, @code{kp-right}, @code{kp-down} |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
989 Keypad arrow keys. Emacs normally translates these into the |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
990 corresponding non-keypad keys @code{home}, @code{left}, @dots{} |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
991 @item @code{kp-prior}, @code{kp-next}, @code{kp-end}, @code{kp-begin}, @code{kp-insert}, @code{kp-delete} |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
992 Additional keypad duplicates of keys ordinarily found elsewhere. Emacs |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
993 normally translates these into the like-named non-keypad keys. |
6260 | 994 @end table |
995 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
996 You can use the modifier keys @key{ALT}, @key{CTRL}, @key{HYPER}, |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
997 @key{META}, @key{SHIFT}, and @key{SUPER} with function keys. The way to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
998 represent them is with prefixes in the symbol name: |
6260 | 999 |
1000 @table @samp | |
1001 @item A- | |
1002 The alt modifier. | |
1003 @item C- | |
1004 The control modifier. | |
1005 @item H- | |
1006 The hyper modifier. | |
1007 @item M- | |
1008 The meta modifier. | |
1009 @item S- | |
1010 The shift modifier. | |
1011 @item s- | |
1012 The super modifier. | |
1013 @end table | |
1014 | |
1015 Thus, the symbol for the key @key{F3} with @key{META} held down is | |
8532 | 1016 @code{M-f3}. When you use more than one prefix, we recommend you |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1017 write them in alphabetical order; but the order does not matter in |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1018 arguments to the key-binding lookup and modification functions. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1019 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1020 @node Mouse Events |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1021 @subsection Mouse Events |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1022 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1023 Emacs supports four kinds of mouse events: click events, drag events, |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1024 button-down events, and motion events. All mouse events are represented |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1025 as lists. The @sc{car} of the list is the event type; this says which |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1026 mouse button was involved, and which modifier keys were used with it. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1027 The event type can also distinguish double or triple button presses |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1028 (@pxref{Repeat Events}). The rest of the list elements give position |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1029 and time information. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1030 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1031 For key lookup, only the event type matters: two events of the same type |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1032 necessarily run the same command. The command can access the full |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1033 values of these events using the @samp{e} interactive code. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1034 @xref{Interactive Codes}. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1035 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1036 A key sequence that starts with a mouse event is read using the keymaps |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1037 of the buffer in the window that the mouse was in, not the current |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1038 buffer. This does not imply that clicking in a window selects that |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1039 window or its buffer---that is entirely under the control of the command |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1040 binding of the key sequence. |
6260 | 1041 |
1042 @node Click Events | |
1043 @subsection Click Events | |
1044 @cindex click event | |
1045 @cindex mouse click event | |
1046 | |
1047 When the user presses a mouse button and releases it at the same | |
1048 location, that generates a @dfn{click} event. Mouse click events have | |
1049 this form: | |
1050 | |
1051 @example | |
1052 (@var{event-type} | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1053 (@var{window} @var{buffer-pos} (@var{x} . @var{y}) @var{timestamp}) |
6260 | 1054 @var{click-count}) |
1055 @end example | |
1056 | |
1057 Here is what the elements normally mean: | |
1058 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1059 @table @asis |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1060 @item @var{event-type} |
6260 | 1061 This is a symbol that indicates which mouse button was used. It is |
1062 one of the symbols @code{mouse-1}, @code{mouse-2}, @dots{}, where the | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1063 buttons are numbered left to right. |
6260 | 1064 |
1065 You can also use prefixes @samp{A-}, @samp{C-}, @samp{H-}, @samp{M-}, | |
1066 @samp{S-} and @samp{s-} for modifiers alt, control, hyper, meta, shift | |
1067 and super, just as you would with function keys. | |
1068 | |
1069 This symbol also serves as the event type of the event. Key bindings | |
1070 describe events by their types; thus, if there is a key binding for | |
1071 @code{mouse-1}, that binding would apply to all events whose | |
1072 @var{event-type} is @code{mouse-1}. | |
1073 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1074 @item @var{window} |
6260 | 1075 This is the window in which the click occurred. |
1076 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1077 @item @var{x}, @var{y} |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1078 These are the pixel-denominated coordinates of the click, relative to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1079 the top left corner of @var{window}, which is @code{(0 . 0)}. |
6260 | 1080 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1081 @item @var{buffer-pos} |
6260 | 1082 This is the buffer position of the character clicked on. |
1083 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1084 @item @var{timestamp} |
6260 | 1085 This is the time at which the event occurred, in milliseconds. (Since |
1086 this value wraps around the entire range of Emacs Lisp integers in about | |
1087 five hours, it is useful only for relating the times of nearby events.) | |
1088 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1089 @item @var{click-count} |
6260 | 1090 This is the number of rapid repeated presses so far of the same mouse |
1091 button. @xref{Repeat Events}. | |
1092 @end table | |
1093 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1094 The meanings of @var{buffer-pos}, @var{x} and @var{y} are somewhat |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1095 different when the event location is in a special part of the screen, |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1096 such as the mode line or a scroll bar. |
6260 | 1097 |
1098 If the location is in a scroll bar, then @var{buffer-pos} is the symbol | |
1099 @code{vertical-scroll-bar} or @code{horizontal-scroll-bar}, and the pair | |
1100 @code{(@var{x} . @var{y})} is replaced with a pair @code{(@var{portion} | |
1101 . @var{whole})}, where @var{portion} is the distance of the click from | |
1102 the top or left end of the scroll bar, and @var{whole} is the length of | |
1103 the entire scroll bar. | |
1104 | |
1105 If the position is on a mode line or the vertical line separating | |
1106 @var{window} from its neighbor to the right, then @var{buffer-pos} is | |
1107 the symbol @code{mode-line} or @code{vertical-line}. For the mode line, | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1108 @var{y} does not have meaningful data. For the vertical line, @var{x} |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1109 does not have meaningful data. |
6260 | 1110 |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1111 In one special case, @var{buffer-pos} is a list containing a symbol (one |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1112 of the symbols listed above) instead of just the symbol. This happens |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1113 after the imaginary prefix keys for the event are inserted into the |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1114 input stream. @xref{Key Sequence Input}. |
6260 | 1115 |
1116 @node Drag Events | |
1117 @subsection Drag Events | |
1118 @cindex drag event | |
1119 @cindex mouse drag event | |
1120 | |
1121 With Emacs, you can have a drag event without even changing your | |
1122 clothes. A @dfn{drag event} happens every time the user presses a mouse | |
1123 button and then moves the mouse to a different character position before | |
1124 releasing the button. Like all mouse events, drag events are | |
1125 represented in Lisp as lists. The lists record both the starting mouse | |
1126 position and the final position, like this: | |
1127 | |
1128 @example | |
1129 (@var{event-type} | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1130 (@var{window1} @var{buffer-pos1} (@var{x1} . @var{y1}) @var{timestamp1}) |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1131 (@var{window2} @var{buffer-pos2} (@var{x2} . @var{y2}) @var{timestamp2}) |
6260 | 1132 @var{click-count}) |
1133 @end example | |
1134 | |
1135 For a drag event, the name of the symbol @var{event-type} contains the | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1136 prefix @samp{drag-}. For example, dragging the mouse with button 2 held |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1137 down generates a @code{drag-mouse-2} event. The second and third |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1138 elements of the event give the starting and ending position of the drag. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1139 Aside from that, the data have the same meanings as in a click event |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1140 (@pxref{Click Events}). You can access the second element of any mouse |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1141 event in the same way, with no need to distinguish drag events from |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1142 others. |
6260 | 1143 |
1144 The @samp{drag-} prefix follows the modifier key prefixes such as | |
1145 @samp{C-} and @samp{M-}. | |
1146 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1147 If @code{read-key-sequence} receives a drag event that has no key |
6260 | 1148 binding, and the corresponding click event does have a binding, it |
1149 changes the drag event into a click event at the drag's starting | |
1150 position. This means that you don't have to distinguish between click | |
1151 and drag events unless you want to. | |
1152 | |
1153 @node Button-Down Events | |
1154 @subsection Button-Down Events | |
1155 @cindex button-down event | |
1156 | |
1157 Click and drag events happen when the user releases a mouse button. | |
1158 They cannot happen earlier, because there is no way to distinguish a | |
1159 click from a drag until the button is released. | |
1160 | |
1161 If you want to take action as soon as a button is pressed, you need to | |
1162 handle @dfn{button-down} events.@footnote{Button-down is the | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1163 conservative antithesis of drag.} These occur as soon as a button is |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1164 pressed. They are represented by lists that look exactly like click |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1165 events (@pxref{Click Events}), except that the @var{event-type} symbol |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1166 name contains the prefix @samp{down-}. The @samp{down-} prefix follows |
6260 | 1167 modifier key prefixes such as @samp{C-} and @samp{M-}. |
1168 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1169 The function @code{read-key-sequence} ignores any button-down events |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1170 that don't have command bindings; therefore, the Emacs command loop |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1171 ignores them too. This means that you need not worry about defining |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1172 button-down events unless you want them to do something. The usual |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1173 reason to define a button-down event is so that you can track mouse |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1174 motion (by reading motion events) until the button is released. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1175 @xref{Motion Events}. |
6260 | 1176 |
1177 @node Repeat Events | |
1178 @subsection Repeat Events | |
1179 @cindex repeat events | |
1180 @cindex double-click events | |
1181 @cindex triple-click events | |
1182 | |
1183 If you press the same mouse button more than once in quick succession | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1184 without moving the mouse, Emacs generates special @dfn{repeat} mouse |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1185 events for the second and subsequent presses. |
6260 | 1186 |
1187 The most common repeat events are @dfn{double-click} events. Emacs | |
1188 generates a double-click event when you click a button twice; the event | |
1189 happens when you release the button (as is normal for all click | |
1190 events). | |
1191 | |
1192 The event type of a double-click event contains the prefix | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1193 @samp{double-}. Thus, a double click on the second mouse button with |
6260 | 1194 @key{meta} held down comes to the Lisp program as |
1195 @code{M-double-mouse-2}. If a double-click event has no binding, the | |
1196 binding of the corresponding ordinary click event is used to execute | |
1197 it. Thus, you need not pay attention to the double click feature | |
1198 unless you really want to. | |
1199 | |
1200 When the user performs a double click, Emacs generates first an ordinary | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1201 click event, and then a double-click event. Therefore, you must design |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1202 the command binding of the double click event to assume that the |
6260 | 1203 single-click command has already run. It must produce the desired |
1204 results of a double click, starting from the results of a single click. | |
1205 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1206 This is convenient, if the meaning of a double click somehow ``builds |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1207 on'' the meaning of a single click---which is recommended user interface |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1208 design practice for double clicks. |
6260 | 1209 |
1210 If you click a button, then press it down again and start moving the | |
1211 mouse with the button held down, then you get a @dfn{double-drag} event | |
1212 when you ultimately release the button. Its event type contains | |
1213 @samp{double-drag} instead of just @samp{drag}. If a double-drag event | |
1214 has no binding, Emacs looks for an alternate binding as if the event | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1215 were an ordinary drag. |
6260 | 1216 |
1217 Before the double-click or double-drag event, Emacs generates a | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1218 @dfn{double-down} event when the user presses the button down for the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1219 second time. Its event type contains @samp{double-down} instead of just |
6260 | 1220 @samp{down}. If a double-down event has no binding, Emacs looks for an |
1221 alternate binding as if the event were an ordinary button-down event. | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1222 If it finds no binding that way either, the double-down event is |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1223 ignored. |
6260 | 1224 |
1225 To summarize, when you click a button and then press it again right | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1226 away, Emacs generates a down event and a click event for the first |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1227 click, a double-down event when you press the button again, and finally |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1228 either a double-click or a double-drag event. |
6260 | 1229 |
1230 If you click a button twice and then press it again, all in quick | |
1231 succession, Emacs generates a @dfn{triple-down} event, followed by | |
1232 either a @dfn{triple-click} or a @dfn{triple-drag}. The event types of | |
1233 these events contain @samp{triple} instead of @samp{double}. If any | |
1234 triple event has no binding, Emacs uses the binding that it would use | |
1235 for the corresponding double event. | |
1236 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1237 If you click a button three or more times and then press it again, the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1238 events for the presses beyond the third are all triple events. Emacs |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1239 does not have separate event types for quadruple, quintuple, etc.@: |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1240 events. However, you can look at the event list to find out precisely |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1241 how many times the button was pressed. |
6260 | 1242 |
1243 @defun event-click-count event | |
1244 This function returns the number of consecutive button presses that led | |
1245 up to @var{event}. If @var{event} is a double-down, double-click or | |
1246 double-drag event, the value is 2. If @var{event} is a triple event, | |
1247 the value is 3 or greater. If @var{event} is an ordinary mouse event | |
1248 (not a repeat event), the value is 1. | |
1249 @end defun | |
1250 | |
1251 @defvar double-click-time | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1252 To generate repeat events, successive mouse button presses must be at |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1253 the same screen position, and the number of milliseconds between |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1254 successive button presses must be less than the value of |
6260 | 1255 @code{double-click-time}. Setting @code{double-click-time} to |
1256 @code{nil} disables multi-click detection entirely. Setting it to | |
1257 @code{t} removes the time limit; Emacs then detects multi-clicks by | |
1258 position only. | |
1259 @end defvar | |
1260 | |
1261 @node Motion Events | |
1262 @subsection Motion Events | |
1263 @cindex motion event | |
1264 @cindex mouse motion events | |
1265 | |
1266 Emacs sometimes generates @dfn{mouse motion} events to describe motion | |
1267 of the mouse without any button activity. Mouse motion events are | |
1268 represented by lists that look like this: | |
1269 | |
1270 @example | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1271 (mouse-movement (@var{window} @var{buffer-pos} (@var{x} . @var{y}) @var{timestamp})) |
6260 | 1272 @end example |
1273 | |
1274 The second element of the list describes the current position of the | |
1275 mouse, just as in a click event (@pxref{Click Events}). | |
1276 | |
1277 The special form @code{track-mouse} enables generation of motion events | |
1278 within its body. Outside of @code{track-mouse} forms, Emacs does not | |
1279 generate events for mere motion of the mouse, and these events do not | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1280 appear. @xref{Mouse Tracking}. |
6260 | 1281 |
1282 @node Focus Events | |
1283 @subsection Focus Events | |
1284 @cindex focus event | |
1285 | |
1286 Window systems provide general ways for the user to control which window | |
1287 gets keyboard input. This choice of window is called the @dfn{focus}. | |
1288 When the user does something to switch between Emacs frames, that | |
1289 generates a @dfn{focus event}. The normal definition of a focus event, | |
1290 in the global keymap, is to select a new frame within Emacs, as the user | |
1291 would expect. @xref{Input Focus}. | |
1292 | |
1293 Focus events are represented in Lisp as lists that look like this: | |
1294 | |
1295 @example | |
1296 (switch-frame @var{new-frame}) | |
1297 @end example | |
1298 | |
1299 @noindent | |
1300 where @var{new-frame} is the frame switched to. | |
1301 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1302 Most X window managers are set up so that just moving the mouse into a |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1303 window is enough to set the focus there. Emacs appears to do this, |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1304 because it changes the cursor to solid in the new frame. However, there |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1305 is no need for the Lisp program to know about the focus change until |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1306 some other kind of input arrives. So Emacs generates a focus event only |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1307 when the user actually types a keyboard key or presses a mouse button in |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1308 the new frame; just moving the mouse between frames does not generate a |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1309 focus event. |
6260 | 1310 |
1311 A focus event in the middle of a key sequence would garble the | |
1312 sequence. So Emacs never generates a focus event in the middle of a key | |
1313 sequence. If the user changes focus in the middle of a key | |
1314 sequence---that is, after a prefix key---then Emacs reorders the events | |
1315 so that the focus event comes either before or after the multi-event key | |
1316 sequence, and not within it. | |
1317 | |
12067 | 1318 @node Misc Events |
1319 @subsection Miscellaneous Window System Events | |
1320 | |
1321 A few other event types represent occurrences within the window system. | |
1322 | |
1323 @table @code | |
1324 @cindex @code{delete-frame} event | |
1325 @item (delete-frame (@var{frame})) | |
1326 This kind of event indicates that the user gave the window manager | |
1327 a command to delete a particular window, which happens to be an Emacs frame. | |
1328 | |
1329 The standard definition of the @code{delete-frame} event is to delete @var{frame}. | |
1330 | |
1331 @cindex @code{iconify-frame} event | |
1332 @item (iconify-frame (@var{frame})) | |
1333 This kind of event indicates that the user iconified @var{frame} using | |
13007 | 1334 the window manager. Its standard definition is @code{ignore}; since the |
1335 frame has already been iconified, Emacs has no work to do. The purpose | |
1336 of this event type is so that you can keep track of such events if you | |
1337 want to. | |
12067 | 1338 |
12285
1aad1cc93e3f
make-frame-visible event was misdescribed as deiconify-frame.
Richard M. Stallman <rms@gnu.org>
parents:
12282
diff
changeset
|
1339 @cindex @code{make-frame-visible} event |
1aad1cc93e3f
make-frame-visible event was misdescribed as deiconify-frame.
Richard M. Stallman <rms@gnu.org>
parents:
12282
diff
changeset
|
1340 @item (make-frame-visible (@var{frame})) |
12067 | 1341 This kind of event indicates that the user deiconified @var{frame} using |
1342 the window manager. Its standard definition is @code{ignore}; since the | |
13007 | 1343 frame has already been made visible, Emacs has no work to do. |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1344 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1345 @cindex @code{mouse-wheel} event |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1346 @item (mouse-wheel @var{position} @var{delta}) |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1347 This kind of event is generated by moving a wheel on a mouse (such as |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1348 the MS Intellimouse). Its effect is typically a kind of scroll or zoom. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1349 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1350 The element @var{delta} describes the amount and direction of the wheel |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1351 rotation. Its absolute value is the number of increments by which the |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1352 wheel was rotated. A negative @var{delta} indicates that the wheel was |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1353 rotated backwards, towards the user, and a positive @var{delta} |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1354 indicates that the wheel was rotated forward, away from the user. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1355 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1356 The element @var{position} is a list describing the position of the |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1357 event, in the same format as used in a mouse-click event. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1358 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1359 This kind of event is generated only on some kinds of systems. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1360 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1361 @cindex @code{drag-n-drop} event |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1362 @item (drag-n-drop @var{position} @var{files}) |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1363 This kind of event is generated when a group of files is |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1364 selected in an application outside of Emacs, and then dragged and |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1365 dropped onto an Emacs frame. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1366 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1367 The element @var{position} is a list describing the position of the |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1368 event, in the same format as used in a mouse-click event, and |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1369 @var{files} is the list of file names that were dragged and dropped. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1370 The usual way to handle this event is by visiting these files. |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1371 |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1372 This kind of event is generated, at present, only on some kinds of |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1373 systems. |
12067 | 1374 @end table |
1375 | |
12098 | 1376 If one of these events arrives in the middle of a key sequence---that |
1377 is, after a prefix key---then Emacs reorders the events so that this | |
1378 event comes either before or after the multi-event key sequence, not | |
1379 within it. | |
1380 | |
6260 | 1381 @node Event Examples |
1382 @subsection Event Examples | |
1383 | |
1384 If the user presses and releases the left mouse button over the same | |
1385 location, that generates a sequence of events like this: | |
1386 | |
1387 @smallexample | |
1388 (down-mouse-1 (#<window 18 on NEWS> 2613 (0 . 38) -864320)) | |
1389 (mouse-1 (#<window 18 on NEWS> 2613 (0 . 38) -864180)) | |
1390 @end smallexample | |
1391 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1392 While holding the control key down, the user might hold down the |
6260 | 1393 second mouse button, and drag the mouse from one line to the next. |
1394 That produces two events, as shown here: | |
1395 | |
1396 @smallexample | |
1397 (C-down-mouse-2 (#<window 18 on NEWS> 3440 (0 . 27) -731219)) | |
1398 (C-drag-mouse-2 (#<window 18 on NEWS> 3440 (0 . 27) -731219) | |
1399 (#<window 18 on NEWS> 3510 (0 . 28) -729648)) | |
1400 @end smallexample | |
1401 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1402 While holding down the meta and shift keys, the user might press the |
6260 | 1403 second mouse button on the window's mode line, and then drag the mouse |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1404 into another window. That produces a pair of events like these: |
6260 | 1405 |
1406 @smallexample | |
1407 (M-S-down-mouse-2 (#<window 18 on NEWS> mode-line (33 . 31) -457844)) | |
1408 (M-S-drag-mouse-2 (#<window 18 on NEWS> mode-line (33 . 31) -457844) | |
1409 (#<window 20 on carlton-sanskrit.tex> 161 (33 . 3) | |
1410 -453816)) | |
1411 @end smallexample | |
1412 | |
1413 @node Classifying Events | |
1414 @subsection Classifying Events | |
1415 @cindex event type | |
1416 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1417 Every event has an @dfn{event type}, which classifies the event for |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1418 key binding purposes. For a keyboard event, the event type equals the |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1419 event value; thus, the event type for a character is the character, and |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1420 the event type for a function key symbol is the symbol itself. For |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1421 events that are lists, the event type is the symbol in the @sc{car} of |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1422 the list. Thus, the event type is always a symbol or a character. |
6260 | 1423 |
1424 Two events of the same type are equivalent where key bindings are | |
1425 concerned; thus, they always run the same command. That does not | |
1426 necessarily mean they do the same things, however, as some commands look | |
1427 at the whole event to decide what to do. For example, some commands use | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1428 the location of a mouse event to decide where in the buffer to act. |
6260 | 1429 |
1430 Sometimes broader classifications of events are useful. For example, | |
1431 you might want to ask whether an event involved the @key{META} key, | |
1432 regardless of which other key or mouse button was used. | |
1433 | |
1434 The functions @code{event-modifiers} and @code{event-basic-type} are | |
1435 provided to get such information conveniently. | |
1436 | |
1437 @defun event-modifiers event | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1438 This function returns a list of the modifiers that @var{event} has. The |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1439 modifiers are symbols; they include @code{shift}, @code{control}, |
6260 | 1440 @code{meta}, @code{alt}, @code{hyper} and @code{super}. In addition, |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1441 the modifiers list of a mouse event symbol always contains one of |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1442 @code{click}, @code{drag}, and @code{down}. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1443 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1444 The argument @var{event} may be an entire event object, or just an event |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1445 type. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1446 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1447 Here are some examples: |
6260 | 1448 |
1449 @example | |
1450 (event-modifiers ?a) | |
1451 @result{} nil | |
1452 (event-modifiers ?\C-a) | |
1453 @result{} (control) | |
1454 (event-modifiers ?\C-%) | |
1455 @result{} (control) | |
1456 (event-modifiers ?\C-\S-a) | |
1457 @result{} (control shift) | |
1458 (event-modifiers 'f5) | |
1459 @result{} nil | |
1460 (event-modifiers 's-f5) | |
1461 @result{} (super) | |
1462 (event-modifiers 'M-S-f5) | |
1463 @result{} (meta shift) | |
1464 (event-modifiers 'mouse-1) | |
1465 @result{} (click) | |
1466 (event-modifiers 'down-mouse-1) | |
1467 @result{} (down) | |
1468 @end example | |
1469 | |
1470 The modifiers list for a click event explicitly contains @code{click}, | |
1471 but the event symbol name itself does not contain @samp{click}. | |
1472 @end defun | |
1473 | |
1474 @defun event-basic-type event | |
1475 This function returns the key or mouse button that @var{event} | |
1476 describes, with all modifiers removed. For example: | |
1477 | |
1478 @example | |
1479 (event-basic-type ?a) | |
1480 @result{} 97 | |
1481 (event-basic-type ?A) | |
1482 @result{} 97 | |
1483 (event-basic-type ?\C-a) | |
1484 @result{} 97 | |
1485 (event-basic-type ?\C-\S-a) | |
1486 @result{} 97 | |
1487 (event-basic-type 'f5) | |
1488 @result{} f5 | |
1489 (event-basic-type 's-f5) | |
1490 @result{} f5 | |
1491 (event-basic-type 'M-S-f5) | |
1492 @result{} f5 | |
1493 (event-basic-type 'down-mouse-1) | |
1494 @result{} mouse-1 | |
1495 @end example | |
1496 @end defun | |
1497 | |
1498 @defun mouse-movement-p object | |
1499 This function returns non-@code{nil} if @var{object} is a mouse movement | |
1500 event. | |
1501 @end defun | |
1502 | |
12098 | 1503 @defun event-convert-list list |
1504 This function converts a list of modifier names and a basic event type | |
1505 to an event type which specifies all of them. For example, | |
1506 | |
1507 @example | |
1508 (event-convert-list '(control ?a)) | |
1509 @result{} 1 | |
1510 (event-convert-list '(control meta ?a)) | |
1511 @result{} -134217727 | |
1512 (event-convert-list '(control super f1)) | |
1513 @result{} C-s-f1 | |
1514 @end example | |
1515 @end defun | |
1516 | |
6260 | 1517 @node Accessing Events |
1518 @subsection Accessing Events | |
1519 | |
1520 This section describes convenient functions for accessing the data in | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1521 a mouse button or motion event. |
6260 | 1522 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1523 These two functions return the starting or ending position of a |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1524 mouse-button event, as a list of this form: |
6260 | 1525 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1526 @example |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1527 (@var{window} @var{buffer-position} (@var{x} . @var{y}) @var{timestamp}) |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1528 @end example |
6260 | 1529 |
1530 @defun event-start event | |
1531 This returns the starting position of @var{event}. | |
1532 | |
1533 If @var{event} is a click or button-down event, this returns the | |
1534 location of the event. If @var{event} is a drag event, this returns the | |
1535 drag's starting position. | |
1536 @end defun | |
1537 | |
1538 @defun event-end event | |
1539 This returns the ending position of @var{event}. | |
1540 | |
1541 If @var{event} is a drag event, this returns the position where the user | |
1542 released the mouse button. If @var{event} is a click or button-down | |
1543 event, the value is actually the starting position, which is the only | |
1544 position such events have. | |
1545 @end defun | |
1546 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1547 These five functions take a position list as described above, and |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1548 return various parts of it. |
6260 | 1549 |
1550 @defun posn-window position | |
1551 Return the window that @var{position} is in. | |
1552 @end defun | |
1553 | |
1554 @defun posn-point position | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1555 Return the buffer position in @var{position}. This is an integer. |
6260 | 1556 @end defun |
1557 | |
1558 @defun posn-x-y position | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1559 Return the pixel-based x and y coordinates in @var{position}, as a cons |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1560 cell @code{(@var{x} . @var{y})}. |
6260 | 1561 @end defun |
1562 | |
1563 @defun posn-col-row position | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1564 Return the row and column (in units of characters) of @var{position}, as |
6260 | 1565 a cons cell @code{(@var{col} . @var{row})}. These are computed from the |
1566 @var{x} and @var{y} values actually found in @var{position}. | |
1567 @end defun | |
1568 | |
1569 @defun posn-timestamp position | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1570 Return the timestamp in @var{position}. |
6260 | 1571 @end defun |
1572 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1573 These functions are useful for decoding scroll bar events. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1574 |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1575 @defun scroll-bar-event-ratio event |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1576 This function returns the fractional vertical position of a scroll bar |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1577 event within the scroll bar. The value is a cons cell |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1578 @code{(@var{portion} . @var{whole})} containing two integers whose ratio |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1579 is the fractional position. |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1580 @end defun |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1581 |
6260 | 1582 @defun scroll-bar-scale ratio total |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1583 This function multiplies (in effect) @var{ratio} by @var{total}, |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1584 rounding the result to an integer. The argument @var{ratio} is not a |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1585 number, but rather a pair @code{(@var{num} . @var{denom})}---typically a |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1586 value returned by @code{scroll-bar-event-ratio}. |
6260 | 1587 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1588 This function is handy for scaling a position on a scroll bar into a |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1589 buffer position. Here's how to do that: |
6260 | 1590 |
1591 @example | |
1592 (+ (point-min) | |
1593 (scroll-bar-scale | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1594 (posn-x-y (event-start event)) |
6260 | 1595 (- (point-max) (point-min)))) |
1596 @end example | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1597 |
22252
40089afa2b1d
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22138
diff
changeset
|
1598 Recall that scroll bar events have two integers forming a ratio, in place |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1599 of a pair of x and y coordinates. |
6260 | 1600 @end defun |
1601 | |
1602 @node Strings of Events | |
1603 @subsection Putting Keyboard Events in Strings | |
1604 | |
1605 In most of the places where strings are used, we conceptualize the | |
1606 string as containing text characters---the same kind of characters found | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1607 in buffers or files. Occasionally Lisp programs use strings that |
6260 | 1608 conceptually contain keyboard characters; for example, they may be key |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1609 sequences or keyboard macro definitions. However, storing keyboard |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1610 characters in a string is a complex matter, for reasons of historical |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1611 compatibility, and it is not always possible. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1612 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1613 We recommend that new programs avoid dealing with these complexities |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1614 by not storing keyboard events in strings. Here is how to do that: |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1615 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1616 @itemize @bullet |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1617 @item |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1618 Use vectors instead of strings for key sequences, when you plan to use |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1619 them for anything other than as arguments to @code{lookup-key} and |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1620 @code{define-key}. For example, you can use |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1621 @code{read-key-sequence-vector} instead of @code{read-key-sequence}, and |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1622 @code{this-command-keys-vector} instead of @code{this-command-keys}. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1623 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1624 @item |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1625 Use vectors to write key sequence constants containing meta characters, |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1626 even when passing them directly to @code{define-key}. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1627 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1628 @item |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1629 When you have to look at the contents of a key sequence that might be a |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1630 string, use @code{listify-key-sequence} (@pxref{Event Input Misc}) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1631 first, to convert it to a list. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1632 @end itemize |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1633 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1634 The complexities stem from the modifier bits that keyboard input |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1635 characters can include. Aside from the Meta modifier, none of these |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1636 modifier bits can be included in a string, and the Meta modifier is |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1637 allowed only in special cases. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1638 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1639 The earliest GNU Emacs versions represented meta characters as codes |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1640 in the range of 128 to 255. At that time, the basic character codes |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1641 ranged from 0 to 127, so all keyboard character codes did fit in a |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1642 string. Many Lisp programs used @samp{\M-} in string constants to stand |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1643 for meta characters, especially in arguments to @code{define-key} and |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1644 similar functions, and key sequences and sequences of events were always |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1645 represented as strings. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1646 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1647 When we added support for larger basic character codes beyond 127, and |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1648 additional modifier bits, we had to change the representation of meta |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1649 characters. Now the flag that represents the Meta modifier in a |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1650 character is |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1651 @tex |
12098 | 1652 $2^{27}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1653 @end tex |
12098 | 1654 @ifinfo |
1655 2**27 | |
1656 @end ifinfo | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1657 and such numbers cannot be included in a string. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1658 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1659 To support programs with @samp{\M-} in string constants, there are |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1660 special rules for including certain meta characters in a string. |
22252
40089afa2b1d
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22138
diff
changeset
|
1661 Here are the rules for interpreting a string as a sequence of input |
40089afa2b1d
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22138
diff
changeset
|
1662 characters: |
6260 | 1663 |
1664 @itemize @bullet | |
1665 @item | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1666 If the keyboard character value is in the range of 0 to 127, it can go |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1667 in the string unchanged. |
6260 | 1668 |
1669 @item | |
12098 | 1670 The meta variants of those characters, with codes in the range of |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1671 @tex |
12098 | 1672 $2^{27}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1673 @end tex |
12098 | 1674 @ifinfo |
1675 2**27 | |
1676 @end ifinfo | |
1677 to | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1678 @tex |
12098 | 1679 $2^{27} + 127$, |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1680 @end tex |
12098 | 1681 @ifinfo |
1682 2**27+127, | |
1683 @end ifinfo | |
1684 can also go in the string, but you must change their | |
1685 numeric values. You must set the | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1686 @tex |
12098 | 1687 $2^{7}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1688 @end tex |
12098 | 1689 @ifinfo |
1690 2**7 | |
1691 @end ifinfo | |
1692 bit instead of the | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1693 @tex |
12098 | 1694 $2^{27}$ |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1695 @end tex |
12098 | 1696 @ifinfo |
1697 2**27 | |
1698 @end ifinfo | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1699 bit, resulting in a value between 128 and 255. Only a unibyte string |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1700 can include these codes. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1701 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1702 @item |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1703 Non-@sc{ASCII} characters above 256 can be included in a multibyte string. |
6260 | 1704 |
1705 @item | |
1706 Other keyboard character events cannot fit in a string. This includes | |
1707 keyboard events in the range of 128 to 255. | |
1708 @end itemize | |
1709 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1710 Functions such as @code{read-key-sequence} that construct strings of |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1711 keyboard input characters follow these rules: they construct vectors |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1712 instead of strings, when the events won't fit in a string. |
6260 | 1713 |
1714 When you use the read syntax @samp{\M-} in a string, it produces a | |
1715 code in the range of 128 to 255---the same code that you get if you | |
1716 modify the corresponding keyboard event to put it in the string. Thus, | |
1717 meta events in strings work consistently regardless of how they get into | |
1718 the strings. | |
1719 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1720 However, most programs would do well to avoid these issues by |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1721 following the recommendations at the beginning of this section. |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1722 |
6260 | 1723 @node Reading Input |
1724 @section Reading Input | |
1725 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1726 The editor command loop reads key sequences using the function |
6260 | 1727 @code{read-key-sequence}, which uses @code{read-event}. These and other |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1728 functions for event input are also available for use in Lisp programs. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1729 See also @code{momentary-string-display} in @ref{Temporary Displays}, |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1730 and @code{sit-for} in @ref{Waiting}. @xref{Terminal Input}, for |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1731 functions and variables for controlling terminal input modes and |
15764 | 1732 debugging terminal input. @xref{Translating Input}, for features you |
1733 can use for translating or modifying input events while reading them. | |
6260 | 1734 |
1735 For higher-level input facilities, see @ref{Minibuffers}. | |
1736 | |
1737 @menu | |
1738 * Key Sequence Input:: How to read one key sequence. | |
1739 * Reading One Event:: How to read just one event. | |
1740 * Quoted Character Input:: Asking the user to specify a character. | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1741 * Event Input Misc:: How to reread or throw away input events. |
6260 | 1742 @end menu |
1743 | |
1744 @node Key Sequence Input | |
1745 @subsection Key Sequence Input | |
1746 @cindex key sequence input | |
1747 | |
1748 The command loop reads input a key sequence at a time, by calling | |
1749 @code{read-key-sequence}. Lisp programs can also call this function; | |
1750 for example, @code{describe-key} uses it to read the key to describe. | |
1751 | |
1752 @defun read-key-sequence prompt | |
1753 @cindex key sequence | |
1754 This function reads a key sequence and returns it as a string or | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1755 vector. It keeps reading events until it has accumulated a complete key |
6260 | 1756 sequence; that is, enough to specify a non-prefix command using the |
1757 currently active keymaps. | |
1758 | |
1759 If the events are all characters and all can fit in a string, then | |
1760 @code{read-key-sequence} returns a string (@pxref{Strings of Events}). | |
1761 Otherwise, it returns a vector, since a vector can hold all kinds of | |
1762 events---characters, symbols, and lists. The elements of the string or | |
1763 vector are the events in the key sequence. | |
1764 | |
1765 The argument @var{prompt} is either a string to be displayed in the echo | |
1766 area as a prompt, or @code{nil}, meaning not to display a prompt. | |
1767 | |
1768 In the example below, the prompt @samp{?} is displayed in the echo area, | |
1769 and the user types @kbd{C-x C-f}. | |
1770 | |
1771 @example | |
1772 (read-key-sequence "?") | |
1773 | |
1774 @group | |
1775 ---------- Echo Area ---------- | |
1776 ?@kbd{C-x C-f} | |
1777 ---------- Echo Area ---------- | |
1778 | |
1779 @result{} "^X^F" | |
1780 @end group | |
1781 @end example | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1782 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1783 The function @code{read-key-sequence} suppresses quitting: @kbd{C-g} |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1784 typed while reading with this function works like any other character, |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1785 and does not set @code{quit-flag}. @xref{Quitting}. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1786 @end defun |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1787 |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1788 @defun read-key-sequence-vector prompt |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1789 This is like @code{read-key-sequence} except that it always |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1790 returns the key sequence as a vector, never as a string. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1791 @xref{Strings of Events}. |
6260 | 1792 @end defun |
1793 | |
1794 @cindex upper case key sequence | |
1795 @cindex downcasing in @code{lookup-key} | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1796 If an input character is an upper-case letter and has no key binding, |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1797 but its lower-case equivalent has one, then @code{read-key-sequence} |
6260 | 1798 converts the character to lower case. Note that @code{lookup-key} does |
1799 not perform case conversion in this way. | |
1800 | |
1801 The function @code{read-key-sequence} also transforms some mouse events. | |
1802 It converts unbound drag events into click events, and discards unbound | |
12098 | 1803 button-down events entirely. It also reshuffles focus events and |
1804 miscellaneous window events so that they never appear in a key sequence | |
1805 with any other events. | |
6260 | 1806 |
1807 When mouse events occur in special parts of a window, such as a mode | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1808 line or a scroll bar, the event type shows nothing special---it is the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1809 same symbol that would normally represent that combination of mouse |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1810 button and modifier keys. The information about the window part is kept |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1811 elsewhere in the event---in the coordinates. But |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1812 @code{read-key-sequence} translates this information into imaginary |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1813 ``prefix keys'', all of which are symbols: @code{mode-line}, |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1814 @code{vertical-line}, @code{horizontal-scroll-bar} and |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1815 @code{vertical-scroll-bar}. You can define meanings for mouse clicks in |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1816 special window parts by defining key sequences using these imaginary |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1817 prefix keys. |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1818 |
6260 | 1819 For example, if you call @code{read-key-sequence} and then click the |
12098 | 1820 mouse on the window's mode line, you get two events, like this: |
6260 | 1821 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1822 @example |
6260 | 1823 (read-key-sequence "Click on the mode line: ") |
1824 @result{} [mode-line | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1825 (mouse-1 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1826 (#<window 6 on NEWS> mode-line |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1827 (40 . 63) 5959987))] |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1828 @end example |
6260 | 1829 |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1830 @defvar num-input-keys |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1831 @c Emacs 19 feature |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1832 This variable's value is the number of key sequences processed so far in |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1833 this Emacs session. This includes key sequences read from the terminal |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1834 and key sequences read from keyboard macros being executed. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1835 @end defvar |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1836 |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1837 @defvar num-nonmacro-input-events |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1838 @tindex num-nonmacro-input-events |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1839 This variable holds the total number of input events received so far |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1840 from the terminal---not counting those generated by keyboard macros. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1841 @end defvar |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
1842 |
6260 | 1843 @node Reading One Event |
1844 @subsection Reading One Event | |
1845 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1846 The lowest level functions for command input are those that read a |
6260 | 1847 single event. |
1848 | |
1849 @defun read-event | |
1850 This function reads and returns the next event of command input, waiting | |
1851 if necessary until an event is available. Events can come directly from | |
1852 the user or from a keyboard macro. | |
1853 | |
1854 The function @code{read-event} does not display any message to indicate | |
1855 it is waiting for input; use @code{message} first, if you wish to | |
1856 display one. If you have not displayed a message, @code{read-event} | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1857 prompts by echoing: it displays descriptions of the events that led to |
6260 | 1858 or were read by the current command. @xref{The Echo Area}. |
1859 | |
1860 If @code{cursor-in-echo-area} is non-@code{nil}, then @code{read-event} | |
1861 moves the cursor temporarily to the echo area, to the end of any message | |
1862 displayed there. Otherwise @code{read-event} does not move the cursor. | |
1863 | |
22252
40089afa2b1d
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22138
diff
changeset
|
1864 If @code{read-event} gets an event that is defined as a help character, in |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1865 some cases @code{read-event} processes the event directly without |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1866 returning. @xref{Help Functions}. Certain other events, called |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1867 @dfn{special events}, are also processed directly within |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1868 @code{read-event} (@pxref{Special Events}). |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
1869 |
6260 | 1870 Here is what happens if you call @code{read-event} and then press the |
1871 right-arrow function key: | |
1872 | |
1873 @example | |
1874 @group | |
1875 (read-event) | |
1876 @result{} right | |
1877 @end group | |
1878 @end example | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1879 @end defun |
6260 | 1880 |
1881 @defun read-char | |
1882 This function reads and returns a character of command input. It | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1883 discards any events that are not characters, until it gets a character. |
6260 | 1884 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1885 In the first example, the user types the character @kbd{1} (@sc{ASCII} |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1886 code 49). The second example shows a keyboard macro definition that |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1887 calls @code{read-char} from the minibuffer using @code{eval-expression}. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1888 @code{read-char} reads the keyboard macro's very next character, which |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1889 is @kbd{1}. Then @code{eval-expression} displays its return value in |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1890 the echo area. |
6260 | 1891 |
1892 @example | |
1893 @group | |
1894 (read-char) | |
1895 @result{} 49 | |
1896 @end group | |
1897 | |
1898 @group | |
12098 | 1899 ;; @r{We assume here you use @kbd{M-:} to evaluate this.} |
6260 | 1900 (symbol-function 'foo) |
12098 | 1901 @result{} "^[:(read-char)^M1" |
6260 | 1902 @end group |
1903 @group | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1904 (execute-kbd-macro 'foo) |
6260 | 1905 @print{} 49 |
1906 @result{} nil | |
1907 @end group | |
1908 @end example | |
1909 @end defun | |
1910 | |
22843
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1911 @code{read-event} also invokes the current input method, if any. If |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1912 the value of @code{input-method-function} is non-@code{nil}, it should |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1913 be a function; when @code{read-event} reads a printing character |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1914 (including @key{SPC}) with no modifier bits, it calls that function, |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1915 passing the event as an argument. |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1916 |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1917 @defvar input-method-function |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1918 If this is non-@code{nil}, its value specifies the current input method |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1919 function. |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1920 @end defvar |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1921 |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1922 The input method function should return a list of events which should |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1923 be used as input. (If the list is @code{nil}, that means there is no |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1924 input, so @code{read-event} waits for another event.) These events are |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1925 processed before the events in @code{unread-command-events}. Events |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1926 returned by the input method function are not passed to the input method |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1927 function again, even if they are printing characters with no modifier |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1928 bits. |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1929 |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1930 If the input method function calls @code{read-event} or |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1931 @code{read-key-sequence}, it should bind @code{input-method-function} to |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1932 @code{nil} first, to prevent recursion. |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1933 |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1934 The input method function is not called when reading the second and |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1935 subsequent event of a key sequence. Thus, these characters are not |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1936 subject to input method processing. It is usually a good idea for the |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1937 input method processing to test the values of |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1938 @code{overriding-local-map} and @code{overriding-terminal-local-map}; if |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1939 either of these variables is non-@code{nil}, the input method should put |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1940 its argument into a list and return that list with no further |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1941 processing. |
63f6e25f0cbd
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22440
diff
changeset
|
1942 |
6260 | 1943 @node Quoted Character Input |
1944 @subsection Quoted Character Input | |
1945 @cindex quoted character input | |
1946 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1947 You can use the function @code{read-quoted-char} to ask the user to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1948 specify a character, and allow the user to specify a control or meta |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1949 character conveniently, either literally or as an octal character code. |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1950 The command @code{quoted-insert} uses this function. |
6260 | 1951 |
1952 @defun read-quoted-char &optional prompt | |
1953 @cindex octal character input | |
1954 @cindex control characters, reading | |
1955 @cindex nonprinting characters, reading | |
1956 This function is like @code{read-char}, except that if the first | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1957 character read is an octal digit (0-7), it reads any number of octal |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1958 digits (but stopping if a non-octal digit is found), and returns the |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
1959 character represented by that numeric character code. |
6260 | 1960 |
1961 Quitting is suppressed when the first character is read, so that the | |
1962 user can enter a @kbd{C-g}. @xref{Quitting}. | |
1963 | |
1964 If @var{prompt} is supplied, it specifies a string for prompting the | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1965 user. The prompt string is always displayed in the echo area, followed |
6260 | 1966 by a single @samp{-}. |
1967 | |
1968 In the following example, the user types in the octal number 177 (which | |
1969 is 127 in decimal). | |
1970 | |
1971 @example | |
1972 (read-quoted-char "What character") | |
1973 | |
1974 @group | |
1975 ---------- Echo Area ---------- | |
1976 What character-@kbd{177} | |
1977 ---------- Echo Area ---------- | |
1978 | |
1979 @result{} 127 | |
1980 @end group | |
1981 @end example | |
1982 @end defun | |
1983 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
1984 @need 2000 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1985 @node Event Input Misc |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1986 @subsection Miscellaneous Event Input Features |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1987 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1988 This section describes how to ``peek ahead'' at events without using |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1989 them up, how to check for pending input, and how to discard pending |
22252
40089afa2b1d
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22138
diff
changeset
|
1990 input. See also the function @code{read-passwd} (@pxref{Reading a |
40089afa2b1d
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22138
diff
changeset
|
1991 Password}). |
6260 | 1992 |
1993 @defvar unread-command-events | |
1994 @cindex next input | |
1995 @cindex peeking at input | |
1996 This variable holds a list of events waiting to be read as command | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1997 input. The events are used in the order they appear in the list, and |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
1998 removed one by one as they are used. |
6260 | 1999 |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2000 The variable is needed because in some cases a function reads an event |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2001 and then decides not to use it. Storing the event in this variable |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2002 causes it to be processed normally, by the command loop or by the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2003 functions to read command input. |
6260 | 2004 |
2005 @cindex prefix argument unreading | |
2006 For example, the function that implements numeric prefix arguments reads | |
2007 any number of digits. When it finds a non-digit event, it must unread | |
2008 the event so that it can be read normally by the command loop. | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2009 Likewise, incremental search uses this feature to unread events with no |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2010 special meaning in a search, because these events should exit the search |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2011 and then execute normally. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2012 |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2013 The reliable and easy way to extract events from a key sequence so as to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2014 put them in @code{unread-command-events} is to use |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2015 @code{listify-key-sequence} (@pxref{Strings of Events}). |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2016 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2017 Normally you add events to the front of this list, so that the events |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2018 most recently unread will be reread first. |
6260 | 2019 @end defvar |
2020 | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2021 @defun listify-key-sequence key |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2022 This function converts the string or vector @var{key} to a list of |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2023 individual events, which you can put in @code{unread-command-events}. |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2024 @end defun |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2025 |
6260 | 2026 @defvar unread-command-char |
2027 This variable holds a character to be read as command input. | |
2028 A value of -1 means ``empty''. | |
2029 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2030 This variable is mostly obsolete now that you can use |
6260 | 2031 @code{unread-command-events} instead; it exists only to support programs |
2032 written for Emacs versions 18 and earlier. | |
2033 @end defvar | |
2034 | |
2035 @defun input-pending-p | |
2036 @cindex waiting for command key input | |
2037 This function determines whether any command input is currently | |
2038 available to be read. It returns immediately, with value @code{t} if | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2039 there is available input, @code{nil} otherwise. On rare occasions it |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2040 may return @code{t} when no input is available. |
6260 | 2041 @end defun |
2042 | |
2043 @defvar last-input-event | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2044 @defvarx last-input-char |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2045 This variable records the last terminal input event read, whether |
6260 | 2046 as part of a command or explicitly by a Lisp program. |
2047 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2048 In the example below, the Lisp program reads the character @kbd{1}, |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2049 @sc{ASCII} code 49. It becomes the value of @code{last-input-event}, |
12098 | 2050 while @kbd{C-e} (we assume @kbd{C-x C-e} command is used to evaluate |
2051 this expression) remains the value of @code{last-command-event}. | |
6260 | 2052 |
2053 @example | |
2054 @group | |
2055 (progn (print (read-char)) | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2056 (print last-command-event) |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2057 last-input-event) |
6260 | 2058 @print{} 49 |
2059 @print{} 5 | |
2060 @result{} 49 | |
2061 @end group | |
2062 @end example | |
2063 | |
2064 The alias @code{last-input-char} exists for compatibility with | |
2065 Emacs version 18. | |
2066 @end defvar | |
2067 | |
2068 @defun discard-input | |
2069 @cindex flush input | |
2070 @cindex discard input | |
2071 @cindex terminate keyboard macro | |
2072 This function discards the contents of the terminal input buffer and | |
2073 cancels any keyboard macro that might be in the process of definition. | |
2074 It returns @code{nil}. | |
2075 | |
2076 In the following example, the user may type a number of characters right | |
2077 after starting the evaluation of the form. After the @code{sleep-for} | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2078 finishes sleeping, @code{discard-input} discards any characters typed |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2079 during the sleep. |
6260 | 2080 |
2081 @example | |
2082 (progn (sleep-for 2) | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2083 (discard-input)) |
6260 | 2084 @result{} nil |
2085 @end example | |
2086 @end defun | |
2087 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2088 @node Special Events |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2089 @section Special Events |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2090 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2091 @cindex special events |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2092 Special events are handled at a very low level---as soon as they are |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2093 read. The @code{read-event} function processes these events itself, and |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2094 never returns them. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2095 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2096 Events that are handled in this way do not echo, they are never grouped |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2097 into key sequences, and they never appear in the value of |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2098 @code{last-command-event} or @code{(this-command-keys)}. They do not |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2099 discard a numeric argument, they cannot be unread with |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2100 @code{unread-command-events}, they may not appear in a keyboard macro, |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2101 and they are not recorded in a keyboard macro while you are defining |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2102 one. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2103 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2104 These events do, however, appear in @code{last-input-event} immediately |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2105 after they are read, and this is the way for the event's definition to |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2106 find the actual event. |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2107 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2108 The events types @code{iconify-frame}, @code{make-frame-visible} and |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2109 @code{delete-frame} are normally handled in this way. The keymap which |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2110 defines how to handle special events---and which events are special---is |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2111 in the variable @code{special-event-map} (@pxref{Active Keymaps}). |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2112 |
6260 | 2113 @node Waiting |
2114 @section Waiting for Elapsed Time or Input | |
2115 @cindex pausing | |
2116 @cindex waiting | |
2117 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2118 The wait functions are designed to wait for a certain amount of time |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2119 to pass or until there is input. For example, you may wish to pause in |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2120 the middle of a computation to allow the user time to view the display. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2121 @code{sit-for} pauses and updates the screen, and returns immediately if |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2122 input comes in, while @code{sleep-for} pauses without updating the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2123 screen. |
6260 | 2124 |
2125 @defun sit-for seconds &optional millisec nodisp | |
2126 This function performs redisplay (provided there is no pending input | |
2127 from the user), then waits @var{seconds} seconds, or until input is | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2128 available. The value is @code{t} if @code{sit-for} waited the full |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2129 time with no input arriving (see @code{input-pending-p} in @ref{Event |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2130 Input Misc}). Otherwise, the value is @code{nil}. |
6260 | 2131 |
12098 | 2132 The argument @var{seconds} need not be an integer. If it is a floating |
2133 point number, @code{sit-for} waits for a fractional number of seconds. | |
2134 Some systems support only a whole number of seconds; on these systems, | |
2135 @var{seconds} is rounded down. | |
2136 | |
6260 | 2137 The optional argument @var{millisec} specifies an additional waiting |
2138 period measured in milliseconds. This adds to the period specified by | |
12098 | 2139 @var{seconds}. If the system doesn't support waiting fractions of a |
2140 second, you get an error if you specify nonzero @var{millisec}. | |
6260 | 2141 |
2142 @cindex forcing redisplay | |
2143 Redisplay is always preempted if input arrives, and does not happen at | |
2144 all if input is available before it starts. Thus, there is no way to | |
2145 force screen updating if there is pending input; however, if there is no | |
2146 input pending, you can force an update with no delay by using | |
2147 @code{(sit-for 0)}. | |
2148 | |
2149 If @var{nodisp} is non-@code{nil}, then @code{sit-for} does not | |
2150 redisplay, but it still returns as soon as input is available (or when | |
2151 the timeout elapses). | |
2152 | |
12067 | 2153 Iconifying or deiconifying a frame makes @code{sit-for} return, because |
2154 that generates an event. @xref{Misc Events}. | |
2155 | |
6260 | 2156 The usual purpose of @code{sit-for} is to give the user time to read |
2157 text that you display. | |
2158 @end defun | |
2159 | |
2160 @defun sleep-for seconds &optional millisec | |
2161 This function simply pauses for @var{seconds} seconds without updating | |
2162 the display. It pays no attention to available input. It returns | |
2163 @code{nil}. | |
2164 | |
12098 | 2165 The argument @var{seconds} need not be an integer. If it is a floating |
2166 point number, @code{sleep-for} waits for a fractional number of seconds. | |
2167 Some systems support only a whole number of seconds; on these systems, | |
2168 @var{seconds} is rounded down. | |
2169 | |
6260 | 2170 The optional argument @var{millisec} specifies an additional waiting |
2171 period measured in milliseconds. This adds to the period specified by | |
12098 | 2172 @var{seconds}. If the system doesn't support waiting fractions of a |
2173 second, you get an error if you specify nonzero @var{millisec}. | |
6260 | 2174 |
2175 Use @code{sleep-for} when you wish to guarantee a delay. | |
2176 @end defun | |
2177 | |
2178 @xref{Time of Day}, for functions to get the current time. | |
2179 | |
2180 @node Quitting | |
2181 @section Quitting | |
2182 @cindex @kbd{C-g} | |
2183 @cindex quitting | |
2184 | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2185 Typing @kbd{C-g} while a Lisp function is running causes Emacs to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2186 @dfn{quit} whatever it is doing. This means that control returns to the |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2187 innermost active command loop. |
6260 | 2188 |
2189 Typing @kbd{C-g} while the command loop is waiting for keyboard input | |
2190 does not cause a quit; it acts as an ordinary input character. In the | |
2191 simplest case, you cannot tell the difference, because @kbd{C-g} | |
2192 normally runs the command @code{keyboard-quit}, whose effect is to quit. | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2193 However, when @kbd{C-g} follows a prefix key, they combine to form an |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2194 undefined key. The effect is to cancel the prefix key as well as any |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2195 prefix argument. |
6260 | 2196 |
2197 In the minibuffer, @kbd{C-g} has a different definition: it aborts out | |
2198 of the minibuffer. This means, in effect, that it exits the minibuffer | |
2199 and then quits. (Simply quitting would return to the command loop | |
2200 @emph{within} the minibuffer.) The reason why @kbd{C-g} does not quit | |
2201 directly when the command reader is reading input is so that its meaning | |
2202 can be redefined in the minibuffer in this way. @kbd{C-g} following a | |
2203 prefix key is not redefined in the minibuffer, and it has its normal | |
2204 effect of canceling the prefix key and prefix argument. This too | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2205 would not be possible if @kbd{C-g} always quit directly. |
6260 | 2206 |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2207 When @kbd{C-g} does directly quit, it does so by setting the variable |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2208 @code{quit-flag} to @code{t}. Emacs checks this variable at appropriate |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2209 times and quits if it is not @code{nil}. Setting @code{quit-flag} |
6260 | 2210 non-@code{nil} in any way thus causes a quit. |
2211 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2212 At the level of C code, quitting cannot happen just anywhere; only at the |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2213 special places that check @code{quit-flag}. The reason for this is |
6260 | 2214 that quitting at other places might leave an inconsistency in Emacs's |
2215 internal state. Because quitting is delayed until a safe place, quitting | |
2216 cannot make Emacs crash. | |
2217 | |
2218 Certain functions such as @code{read-key-sequence} or | |
2219 @code{read-quoted-char} prevent quitting entirely even though they wait | |
2220 for input. Instead of quitting, @kbd{C-g} serves as the requested | |
2221 input. In the case of @code{read-key-sequence}, this serves to bring | |
2222 about the special behavior of @kbd{C-g} in the command loop. In the | |
2223 case of @code{read-quoted-char}, this is so that @kbd{C-q} can be used | |
2224 to quote a @kbd{C-g}. | |
2225 | |
2226 You can prevent quitting for a portion of a Lisp function by binding | |
2227 the variable @code{inhibit-quit} to a non-@code{nil} value. Then, | |
2228 although @kbd{C-g} still sets @code{quit-flag} to @code{t} as usual, the | |
2229 usual result of this---a quit---is prevented. Eventually, | |
2230 @code{inhibit-quit} will become @code{nil} again, such as when its | |
2231 binding is unwound at the end of a @code{let} form. At that time, if | |
2232 @code{quit-flag} is still non-@code{nil}, the requested quit happens | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2233 immediately. This behavior is ideal when you wish to make sure that |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2234 quitting does not happen within a ``critical section'' of the program. |
6260 | 2235 |
2236 @cindex @code{read-quoted-char} quitting | |
2237 In some functions (such as @code{read-quoted-char}), @kbd{C-g} is | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2238 handled in a special way that does not involve quitting. This is done |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2239 by reading the input with @code{inhibit-quit} bound to @code{t}, and |
6260 | 2240 setting @code{quit-flag} to @code{nil} before @code{inhibit-quit} |
2241 becomes @code{nil} again. This excerpt from the definition of | |
2242 @code{read-quoted-char} shows how this is done; it also shows that | |
2243 normal quitting is permitted after the first character of input. | |
2244 | |
2245 @example | |
2246 (defun read-quoted-char (&optional prompt) | |
2247 "@dots{}@var{documentation}@dots{}" | |
21682
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2248 (let ((message-log-max nil) done (first t) (code 0) char) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2249 (while (not done) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2250 (let ((inhibit-quit first) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2251 @dots{}) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2252 (and prompt (message "%s-" prompt)) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2253 (setq char (read-event)) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2254 (if inhibit-quit (setq quit-flag nil))) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2255 @r{@dots{}set the variable @code{code}@dots{}}) |
90da2489c498
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21007
diff
changeset
|
2256 code)) |
6260 | 2257 @end example |
2258 | |
2259 @defvar quit-flag | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2260 If this variable is non-@code{nil}, then Emacs quits immediately, unless |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2261 @code{inhibit-quit} is non-@code{nil}. Typing @kbd{C-g} ordinarily sets |
6260 | 2262 @code{quit-flag} non-@code{nil}, regardless of @code{inhibit-quit}. |
2263 @end defvar | |
2264 | |
2265 @defvar inhibit-quit | |
2266 This variable determines whether Emacs should quit when @code{quit-flag} | |
2267 is set to a value other than @code{nil}. If @code{inhibit-quit} is | |
2268 non-@code{nil}, then @code{quit-flag} has no special effect. | |
2269 @end defvar | |
2270 | |
2271 @deffn Command keyboard-quit | |
2272 This function signals the @code{quit} condition with @code{(signal 'quit | |
2273 nil)}. This is the same thing that quitting does. (See @code{signal} | |
2274 in @ref{Errors}.) | |
2275 @end deffn | |
2276 | |
2277 You can specify a character other than @kbd{C-g} to use for quitting. | |
2278 See the function @code{set-input-mode} in @ref{Terminal Input}. | |
2279 | |
2280 @node Prefix Command Arguments | |
2281 @section Prefix Command Arguments | |
2282 @cindex prefix argument | |
2283 @cindex raw prefix argument | |
2284 @cindex numeric prefix argument | |
2285 | |
2286 Most Emacs commands can use a @dfn{prefix argument}, a number | |
2287 specified before the command itself. (Don't confuse prefix arguments | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2288 with prefix keys.) The prefix argument is at all times represented by a |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2289 value, which may be @code{nil}, meaning there is currently no prefix |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2290 argument. Each command may use the prefix argument or ignore it. |
6260 | 2291 |
2292 There are two representations of the prefix argument: @dfn{raw} and | |
2293 @dfn{numeric}. The editor command loop uses the raw representation | |
2294 internally, and so do the Lisp variables that store the information, but | |
2295 commands can request either representation. | |
2296 | |
2297 Here are the possible values of a raw prefix argument: | |
2298 | |
2299 @itemize @bullet | |
2300 @item | |
2301 @code{nil}, meaning there is no prefix argument. Its numeric value is | |
2302 1, but numerous commands make a distinction between @code{nil} and the | |
2303 integer 1. | |
2304 | |
2305 @item | |
2306 An integer, which stands for itself. | |
2307 | |
2308 @item | |
2309 A list of one element, which is an integer. This form of prefix | |
2310 argument results from one or a succession of @kbd{C-u}'s with no | |
2311 digits. The numeric value is the integer in the list, but some | |
2312 commands make a distinction between such a list and an integer alone. | |
2313 | |
2314 @item | |
2315 The symbol @code{-}. This indicates that @kbd{M--} or @kbd{C-u -} was | |
2316 typed, without following digits. The equivalent numeric value is | |
2317 @minus{}1, but some commands make a distinction between the integer | |
2318 @minus{}1 and the symbol @code{-}. | |
2319 @end itemize | |
2320 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2321 We illustrate these possibilities by calling the following function with |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2322 various prefixes: |
6260 | 2323 |
2324 @example | |
2325 @group | |
2326 (defun display-prefix (arg) | |
2327 "Display the value of the raw prefix arg." | |
2328 (interactive "P") | |
2329 (message "%s" arg)) | |
2330 @end group | |
2331 @end example | |
2332 | |
2333 @noindent | |
2334 Here are the results of calling @code{display-prefix} with various | |
2335 raw prefix arguments: | |
2336 | |
2337 @example | |
2338 M-x display-prefix @print{} nil | |
2339 | |
2340 C-u M-x display-prefix @print{} (4) | |
2341 | |
2342 C-u C-u M-x display-prefix @print{} (16) | |
2343 | |
2344 C-u 3 M-x display-prefix @print{} 3 | |
2345 | |
2346 M-3 M-x display-prefix @print{} 3 ; @r{(Same as @code{C-u 3}.)} | |
2347 | |
2348 C-u - M-x display-prefix @print{} - | |
2349 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2350 M-- M-x display-prefix @print{} - ; @r{(Same as @code{C-u -}.)} |
6260 | 2351 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2352 C-u - 7 M-x display-prefix @print{} -7 |
6260 | 2353 |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2354 M-- 7 M-x display-prefix @print{} -7 ; @r{(Same as @code{C-u -7}.)} |
6260 | 2355 @end example |
2356 | |
2357 Emacs uses two variables to store the prefix argument: | |
2358 @code{prefix-arg} and @code{current-prefix-arg}. Commands such as | |
2359 @code{universal-argument} that set up prefix arguments for other | |
2360 commands store them in @code{prefix-arg}. In contrast, | |
2361 @code{current-prefix-arg} conveys the prefix argument to the current | |
2362 command, so setting it has no effect on the prefix arguments for future | |
2363 commands. | |
2364 | |
2365 Normally, commands specify which representation to use for the prefix | |
2366 argument, either numeric or raw, in the @code{interactive} declaration. | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2367 (@xref{Using Interactive}.) Alternatively, functions may look at the |
6260 | 2368 value of the prefix argument directly in the variable |
2369 @code{current-prefix-arg}, but this is less clean. | |
2370 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2371 @defun prefix-numeric-value arg |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2372 This function returns the numeric meaning of a valid raw prefix argument |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2373 value, @var{arg}. The argument may be a symbol, a number, or a list. |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2374 If it is @code{nil}, the value 1 is returned; if it is @code{-}, the |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2375 value @minus{}1 is returned; if it is a number, that number is returned; |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2376 if it is a list, the @sc{car} of that list (which should be a number) is |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2377 returned. |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2378 @end defun |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2379 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2380 @defvar current-prefix-arg |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2381 This variable holds the raw prefix argument for the @emph{current} |
16736
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
2382 command. Commands may examine it directly, but the usual method for |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
15764
diff
changeset
|
2383 accessing it is with @code{(interactive "P")}. |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2384 @end defvar |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2385 |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2386 @defvar prefix-arg |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2387 The value of this variable is the raw prefix argument for the |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2388 @emph{next} editing command. Commands such as @code{universal-argument} |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2389 that specify prefix arguments for the following command work by setting |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2390 this variable. |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2391 @end defvar |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2392 |
22440
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
2393 @tindex last-prefix-arg |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
2394 @defvar last-prefix-arg |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
2395 The raw prefix argument value used by the previous command. |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
2396 @end defvar |
8a51f757af2c
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
22252
diff
changeset
|
2397 |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2398 The following commands exist to set up prefix arguments for the |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2399 following command. Do not call them for any other reason. |
6260 | 2400 |
2401 @deffn Command universal-argument | |
2402 This command reads input and specifies a prefix argument for the | |
2403 following command. Don't call this command yourself unless you know | |
2404 what you are doing. | |
2405 @end deffn | |
2406 | |
2407 @deffn Command digit-argument arg | |
2408 This command adds to the prefix argument for the following command. The | |
2409 argument @var{arg} is the raw prefix argument as it was before this | |
2410 command; it is used to compute the updated prefix argument. Don't call | |
2411 this command yourself unless you know what you are doing. | |
2412 @end deffn | |
2413 | |
2414 @deffn Command negative-argument arg | |
2415 This command adds to the numeric argument for the next command. The | |
2416 argument @var{arg} is the raw prefix argument as it was before this | |
2417 command; its value is negated to form the new prefix argument. Don't | |
2418 call this command yourself unless you know what you are doing. | |
2419 @end deffn | |
2420 | |
2421 @node Recursive Editing | |
2422 @section Recursive Editing | |
2423 @cindex recursive command loop | |
2424 @cindex recursive editing level | |
2425 @cindex command loop, recursive | |
2426 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2427 The Emacs command loop is entered automatically when Emacs starts up. |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2428 This top-level invocation of the command loop never exits; it keeps |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2429 running as long as Emacs does. Lisp programs can also invoke the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2430 command loop. Since this makes more than one activation of the command |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2431 loop, we call it @dfn{recursive editing}. A recursive editing level has |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2432 the effect of suspending whatever command invoked it and permitting the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2433 user to do arbitrary editing before resuming that command. |
6260 | 2434 |
2435 The commands available during recursive editing are the same ones | |
2436 available in the top-level editing loop and defined in the keymaps. | |
2437 Only a few special commands exit the recursive editing level; the others | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2438 return to the recursive editing level when they finish. (The special |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2439 commands for exiting are always available, but they do nothing when |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2440 recursive editing is not in progress.) |
6260 | 2441 |
2442 All command loops, including recursive ones, set up all-purpose error | |
2443 handlers so that an error in a command run from the command loop will | |
2444 not exit the loop. | |
2445 | |
2446 @cindex minibuffer input | |
2447 Minibuffer input is a special kind of recursive editing. It has a few | |
2448 special wrinkles, such as enabling display of the minibuffer and the | |
2449 minibuffer window, but fewer than you might suppose. Certain keys | |
2450 behave differently in the minibuffer, but that is only because of the | |
2451 minibuffer's local map; if you switch windows, you get the usual Emacs | |
2452 commands. | |
2453 | |
2454 @cindex @code{throw} example | |
2455 @kindex exit | |
2456 @cindex exit recursive editing | |
2457 @cindex aborting | |
2458 To invoke a recursive editing level, call the function | |
2459 @code{recursive-edit}. This function contains the command loop; it also | |
2460 contains a call to @code{catch} with tag @code{exit}, which makes it | |
2461 possible to exit the recursive editing level by throwing to @code{exit} | |
2462 (@pxref{Catch and Throw}). If you throw a value other than @code{t}, | |
2463 then @code{recursive-edit} returns normally to the function that called | |
2464 it. The command @kbd{C-M-c} (@code{exit-recursive-edit}) does this. | |
2465 Throwing a @code{t} value causes @code{recursive-edit} to quit, so that | |
2466 control returns to the command loop one level up. This is called | |
2467 @dfn{aborting}, and is done by @kbd{C-]} (@code{abort-recursive-edit}). | |
2468 | |
2469 Most applications should not use recursive editing, except as part of | |
2470 using the minibuffer. Usually it is more convenient for the user if you | |
2471 change the major mode of the current buffer temporarily to a special | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2472 major mode, which should have a command to go back to the previous mode. |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2473 (The @kbd{e} command in Rmail uses this technique.) Or, if you wish to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2474 give the user different text to edit ``recursively'', create and select |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2475 a new buffer in a special mode. In this mode, define a command to |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2476 complete the processing and go back to the previous buffer. (The |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2477 @kbd{m} command in Rmail does this.) |
6260 | 2478 |
2479 Recursive edits are useful in debugging. You can insert a call to | |
2480 @code{debug} into a function definition as a sort of breakpoint, so that | |
2481 you can look around when the function gets there. @code{debug} invokes | |
2482 a recursive edit but also provides the other features of the debugger. | |
2483 | |
2484 Recursive editing levels are also used when you type @kbd{C-r} in | |
2485 @code{query-replace} or use @kbd{C-x q} (@code{kbd-macro-query}). | |
2486 | |
2487 @defun recursive-edit | |
2488 @cindex suspend evaluation | |
2489 This function invokes the editor command loop. It is called | |
2490 automatically by the initialization of Emacs, to let the user begin | |
2491 editing. When called from a Lisp program, it enters a recursive editing | |
2492 level. | |
2493 | |
2494 In the following example, the function @code{simple-rec} first | |
2495 advances point one word, then enters a recursive edit, printing out a | |
2496 message in the echo area. The user can then do any editing desired, and | |
2497 then type @kbd{C-M-c} to exit and continue executing @code{simple-rec}. | |
2498 | |
2499 @example | |
2500 (defun simple-rec () | |
2501 (forward-word 1) | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2502 (message "Recursive edit in progress") |
6260 | 2503 (recursive-edit) |
2504 (forward-word 1)) | |
2505 @result{} simple-rec | |
2506 (simple-rec) | |
2507 @result{} nil | |
2508 @end example | |
2509 @end defun | |
2510 | |
2511 @deffn Command exit-recursive-edit | |
2512 This function exits from the innermost recursive edit (including | |
2513 minibuffer input). Its definition is effectively @code{(throw 'exit | |
2514 nil)}. | |
2515 @end deffn | |
2516 | |
2517 @deffn Command abort-recursive-edit | |
2518 This function aborts the command that requested the innermost recursive | |
2519 edit (including minibuffer input), by signaling @code{quit} | |
2520 after exiting the recursive edit. Its definition is effectively | |
2521 @code{(throw 'exit t)}. @xref{Quitting}. | |
2522 @end deffn | |
2523 | |
2524 @deffn Command top-level | |
2525 This function exits all recursive editing levels; it does not return a | |
2526 value, as it jumps completely out of any computation directly back to | |
2527 the main command loop. | |
2528 @end deffn | |
2529 | |
2530 @defun recursion-depth | |
2531 This function returns the current depth of recursive edits. When no | |
2532 recursive edit is active, it returns 0. | |
2533 @end defun | |
2534 | |
2535 @node Disabling Commands | |
2536 @section Disabling Commands | |
2537 @cindex disabled command | |
2538 | |
2539 @dfn{Disabling a command} marks the command as requiring user | |
2540 confirmation before it can be executed. Disabling is used for commands | |
2541 which might be confusing to beginning users, to prevent them from using | |
2542 the commands by accident. | |
2543 | |
2544 @kindex disabled | |
2545 The low-level mechanism for disabling a command is to put a | |
2546 non-@code{nil} @code{disabled} property on the Lisp symbol for the | |
2547 command. These properties are normally set up by the user's | |
2548 @file{.emacs} file with Lisp expressions such as this: | |
2549 | |
2550 @example | |
2551 (put 'upcase-region 'disabled t) | |
2552 @end example | |
2553 | |
2554 @noindent | |
2555 For a few commands, these properties are present by default and may be | |
2556 removed by the @file{.emacs} file. | |
2557 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2558 If the value of the @code{disabled} property is a string, the message |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2559 saying the command is disabled includes that string. For example: |
6260 | 2560 |
2561 @example | |
2562 (put 'delete-region 'disabled | |
2563 "Text deleted this way cannot be yanked back!\n") | |
2564 @end example | |
2565 | |
2566 @xref{Disabling,,, emacs, The GNU Emacs Manual}, for the details on | |
2567 what happens when a disabled command is invoked interactively. | |
2568 Disabling a command has no effect on calling it as a function from Lisp | |
2569 programs. | |
2570 | |
2571 @deffn Command enable-command command | |
2572 Allow @var{command} to be executed without special confirmation from now | |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2573 on, and (if the user confirms) alter the user's @file{.emacs} file so |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2574 that this will apply to future sessions. |
6260 | 2575 @end deffn |
2576 | |
2577 @deffn Command disable-command command | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2578 Require special confirmation to execute @var{command} from now on, and |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2579 (if the user confirms) alter the user's @file{.emacs} file so that this |
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2580 will apply to future sessions. |
6260 | 2581 @end deffn |
2582 | |
2583 @defvar disabled-command-hook | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2584 When the user invokes a disabled command interactively, this normal hook |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2585 is run instead of the disabled command. The hook functions can use |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2586 @code{this-command-keys} to determine what the user typed to run the |
7735
7db892210924
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6557
diff
changeset
|
2587 command, and thus find the command itself. @xref{Hooks}. |
6260 | 2588 |
2589 By default, @code{disabled-command-hook} contains a function that asks | |
2590 the user whether to proceed. | |
2591 @end defvar | |
2592 | |
2593 @node Command History | |
2594 @section Command History | |
2595 @cindex command history | |
2596 @cindex complex command | |
2597 @cindex history of commands | |
2598 | |
2599 The command loop keeps a history of the complex commands that have | |
2600 been executed, to make it convenient to repeat these commands. A | |
2601 @dfn{complex command} is one for which the interactive argument reading | |
2602 uses the minibuffer. This includes any @kbd{M-x} command, any | |
12098 | 2603 @kbd{M-:} command, and any command whose @code{interactive} |
6260 | 2604 specification reads an argument from the minibuffer. Explicit use of |
2605 the minibuffer during the execution of the command itself does not cause | |
2606 the command to be considered complex. | |
2607 | |
2608 @defvar command-history | |
2609 This variable's value is a list of recent complex commands, each | |
2610 represented as a form to evaluate. It continues to accumulate all | |
22138
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
2611 complex commands for the duration of the editing session, but when it |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
2612 reaches the maximum size (specified by the variable |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
2613 @code{history-length}), the oldest elements are deleted as new ones are |
d4ac295a98b3
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
21682
diff
changeset
|
2614 added. |
6260 | 2615 |
2616 @example | |
2617 @group | |
2618 command-history | |
2619 @result{} ((switch-to-buffer "chistory.texi") | |
2620 (describe-key "^X^[") | |
2621 (visit-tags-table "~/emacs/src/") | |
2622 (find-tag "repeat-complex-command")) | |
2623 @end group | |
2624 @end example | |
2625 @end defvar | |
2626 | |
2627 This history list is actually a special case of minibuffer history | |
2628 (@pxref{Minibuffer History}), with one special twist: the elements are | |
2629 expressions rather than strings. | |
2630 | |
2631 There are a number of commands devoted to the editing and recall of | |
2632 previous commands. The commands @code{repeat-complex-command}, and | |
2633 @code{list-command-history} are described in the user manual | |
2634 (@pxref{Repetition,,, emacs, The GNU Emacs Manual}). Within the | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2635 minibuffer, the usual minibuffer history commands are available. |
6260 | 2636 |
2637 @node Keyboard Macros | |
2638 @section Keyboard Macros | |
2639 @cindex keyboard macros | |
2640 | |
2641 A @dfn{keyboard macro} is a canned sequence of input events that can | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2642 be considered a command and made the definition of a key. The Lisp |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2643 representation of a keyboard macro is a string or vector containing the |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2644 events. Don't confuse keyboard macros with Lisp macros |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2645 (@pxref{Macros}). |
6260 | 2646 |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2647 @defun execute-kbd-macro kbdmacro &optional count |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2648 This function executes @var{kbdmacro} as a sequence of events. If |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2649 @var{kbdmacro} is a string or vector, then the events in it are executed |
6260 | 2650 exactly as if they had been input by the user. The sequence is |
2651 @emph{not} expected to be a single key sequence; normally a keyboard | |
2652 macro definition consists of several key sequences concatenated. | |
2653 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2654 If @var{kbdmacro} is a symbol, then its function definition is used in |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2655 place of @var{kbdmacro}. If that is another symbol, this process repeats. |
6260 | 2656 Eventually the result should be a string or vector. If the result is |
2657 not a symbol, string, or vector, an error is signaled. | |
2658 | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2659 The argument @var{count} is a repeat count; @var{kbdmacro} is executed that |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2660 many times. If @var{count} is omitted or @code{nil}, @var{kbdmacro} is |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2661 executed once. If it is 0, @var{kbdmacro} is executed over and over until it |
6260 | 2662 encounters an error or a failing search. |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2663 |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2664 @xref{Reading One Event}, for an example of using @code{execute-kbd-macro}. |
6260 | 2665 @end defun |
2666 | |
2667 @defvar executing-macro | |
2668 This variable contains the string or vector that defines the keyboard | |
2669 macro that is currently executing. It is @code{nil} if no macro is | |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2670 currently executing. A command can test this variable so as to behave |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2671 differently when run from an executing macro. Do not set this variable |
6260 | 2672 yourself. |
2673 @end defvar | |
2674 | |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2675 @defvar defining-kbd-macro |
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2676 This variable indicates whether a keyboard macro is being defined. A |
21007
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2677 command can test this variable so as to behave differently while a macro |
66d807bdc5b4
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
2678 is being defined. The commands @code{start-kbd-macro} and |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2679 @code{end-kbd-macro} set this variable---do not set it yourself. |
12067 | 2680 |
12098 | 2681 The variable is always local to the current terminal and cannot be |
12067 | 2682 buffer-local. @xref{Multiple Displays}. |
6557
74758cf67338
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6260
diff
changeset
|
2683 @end defvar |
6260 | 2684 |
12098 | 2685 @defvar last-kbd-macro |
2686 This variable is the definition of the most recently defined keyboard | |
2687 macro. Its value is a string or vector, or @code{nil}. | |
2688 | |
2689 The variable is always local to the current terminal and cannot be | |
2690 buffer-local. @xref{Multiple Displays}. | |
2691 @end defvar | |
2692 |