]> code.delx.au - gnu-emacs/blob - doc/emacs/killing.texi
Merge from trunk.
[gnu-emacs] / doc / emacs / killing.texi
1 @c This is part of the Emacs manual.
2 @c Copyright (C) 1985-1987, 1993-1995, 1997, 2000-2011
3 @c Free Software Foundation, Inc.
4 @c See file emacs.texi for copying conditions.
5
6 @node Killing, Registers, Mark, Top
7 @chapter Killing and Moving Text
8
9 In Emacs, @dfn{killing} means erasing text and copying it into the
10 @dfn{kill ring}. @dfn{Yanking} means bringing text from the kill ring
11 back into the buffer. (Some applications use the terms ``cutting''
12 and ``pasting'' for similar operations.) The kill ring is so-named
13 because it can be visualized as a set of blocks of text arranged in a
14 ring, which you can access in cyclic order. @xref{Kill Ring}.
15
16 Killing and yanking are the most common way to move or copy text
17 within Emacs. It is very versatile, because there are commands for
18 killing many different types of syntactic units.
19
20 @menu
21 * Deletion and Killing:: Commands that remove text.
22 * Yanking:: Commands that insert text.
23 * Cut and Paste:: Clipboard and selections on graphical displays.
24 * Accumulating Text:: Other methods to add text to the buffer.
25 * Rectangles:: Operating on text in rectangular areas.
26 * CUA Bindings:: Using @kbd{C-x}/@kbd{C-c}/@kbd{C-v} to kill and yank.
27 @end menu
28
29 @node Deletion and Killing
30 @section Deletion and Killing
31
32 @cindex killing text
33 @cindex cutting text
34 @cindex deletion
35 Most commands which erase text from the buffer save it in the kill
36 ring. These are known as @dfn{kill} commands, and their names
37 normally contain the word @samp{kill} (e.g. @code{kill-line}). The
38 kill ring stores several recent kills, not just the last one, so
39 killing is a very safe operation: you don't have to worry much about
40 losing text that you previously killed. The kill ring is shared by
41 all buffers, so text that is killed in one buffer can be yanked into
42 another buffer.
43
44 When you use @kbd{C-/} (@code{undo}) to undo a kill command
45 (@pxref{Undo}), that brings the killed text back into the buffer, but
46 does not remove it from the kill ring.
47
48 On graphical displays, killing text also copies it to the system
49 clipboard. @xref{Cut and Paste}.
50
51 Commands that erase text but do not save it in the kill ring are
52 known as @dfn{delete} commands; their names usually contain the word
53 @samp{delete}. These include @kbd{C-d} (@code{delete-char}) and
54 @key{DEL} (@code{delete-backward-char}), which delete only one
55 character at a time, and those commands that delete only spaces or
56 newlines. Commands that can erase significant amounts of nontrivial
57 data generally do a kill operation instead.
58
59 You can also use the mouse to kill and yank. @xref{Cut and Paste}.
60
61 @menu
62 * Deletion:: Commands for deleting small amounts of text and
63 blank areas.
64 * Killing by Lines:: How to kill entire lines of text at one time.
65 * Other Kill Commands:: Commands to kill large regions of text and
66 syntactic units such as words and sentences.
67 * Kill Options:: Options that affect killing.
68 @end menu
69
70 @node Deletion
71 @subsection Deletion
72 @findex delete-backward-char
73 @findex delete-char
74
75 Deletion means erasing text and not saving it in the kill ring. For
76 the most part, the Emacs commands that delete text are those that
77 erase just one character or only whitespace.
78
79 @table @kbd
80 @item @key{DEL}
81 @itemx @key{Backspace}
82 Delete the previous character, or the text in the region if it is
83 active (@code{delete-backward-char}).
84
85 @item @key{Delete}
86 Delete the next character, or the text in the region if it is active
87 (@code{delete-forward-char}).
88
89 @item C-d
90 Delete the next character (@code{delete-char}).
91
92 @item M-\
93 Delete spaces and tabs around point (@code{delete-horizontal-space}).
94 @item M-@key{SPC}
95 Delete spaces and tabs around point, leaving one space
96 (@code{just-one-space}).
97 @item C-x C-o
98 Delete blank lines around the current line (@code{delete-blank-lines}).
99 @item M-^
100 Join two lines by deleting the intervening newline, along with any
101 indentation following it (@code{delete-indentation}).
102 @end table
103
104 We have already described the basic deletion commands @key{DEL}
105 (@code{delete-backward-char}), @key{delete}
106 (@code{delete-forward-char}), and @kbd{C-d} (@code{delete-char}).
107 @xref{Erasing}. With a numeric argument, they delete the specified
108 number of characters. If the numeric argument is omitted or one, they
109 delete all the text in the region if it is active (@pxref{Using
110 Region}).
111
112 @kindex M-\
113 @findex delete-horizontal-space
114 @kindex M-SPC
115 @findex just-one-space
116 The other delete commands are those that delete only whitespace
117 characters: spaces, tabs and newlines. @kbd{M-\}
118 (@code{delete-horizontal-space}) deletes all the spaces and tab
119 characters before and after point. With a prefix argument, this only
120 deletes spaces and tab characters before point. @kbd{M-@key{SPC}}
121 (@code{just-one-space}) does likewise but leaves a single space after
122 point, regardless of the number of spaces that existed previously
123 (even if there were none before). With a numeric argument @var{n}, it
124 leaves @var{n} spaces after point.
125
126 @kbd{C-x C-o} (@code{delete-blank-lines}) deletes all blank lines
127 after the current line. If the current line is blank, it deletes all
128 blank lines preceding the current line as well (leaving one blank line,
129 the current line). On a solitary blank line, it deletes that line.
130
131 @kbd{M-^} (@code{delete-indentation}) joins the current line and the
132 previous line, by deleting a newline and all surrounding spaces, usually
133 leaving a single space. @xref{Indentation,M-^}.
134
135 @node Killing by Lines
136 @subsection Killing by Lines
137
138 @table @kbd
139 @item C-k
140 Kill rest of line or one or more lines (@code{kill-line}).
141 @item C-S-backspace
142 Kill an entire line at once (@code{kill-whole-line})
143 @end table
144
145 @kindex C-k
146 @findex kill-line
147 The simplest kill command is @kbd{C-k} (@code{kill-line}). If used
148 at the end of a line, it kills the line-ending newline character,
149 merging the next line into the current one (thus, a blank line is
150 entirely removed). Otherwise, @kbd{C-k} kills all the text from point
151 up to the end of the line; if point was originally at the beginning of
152 the line, this leaves the line blank.
153
154 Spaces and tabs at the end of the line are ignored when deciding
155 which case applies. As long as point is after the last visible
156 character in the line, you can be sure that @kbd{C-k} will kill the
157 newline. To kill an entire non-blank line, go to the beginning and
158 type @kbd{C-k} twice.
159
160 In this context, ``line'' means a logical text line, not a screen
161 line (@pxref{Continuation Lines}).
162
163 When @kbd{C-k} is given a positive argument @var{n}, it kills
164 @var{n} lines and the newlines that follow them (text on the current
165 line before point is not killed). With a negative argument
166 @minus{}@var{n}, it kills @var{n} lines preceding the current line,
167 together with the text on the current line before point. @kbd{C-k}
168 with an argument of zero kills the text before point on the current
169 line.
170
171 @vindex kill-whole-line
172 If the variable @code{kill-whole-line} is non-@code{nil}, @kbd{C-k} at
173 the very beginning of a line kills the entire line including the
174 following newline. This variable is normally @code{nil}.
175
176 @kindex C-S-backspace
177 @findex kill-whole-line
178 @kbd{C-S-backspace} (@code{kill-whole-line}) kills a whole line
179 including its newline, regardless of the position of point within the
180 line. Note that many text terminals will prevent you from typing the
181 key sequence @kbd{C-S-backspace}.
182
183 @node Other Kill Commands
184 @subsection Other Kill Commands
185 @findex kill-region
186 @kindex C-w
187
188 @table @kbd
189 @item C-w
190 Kill the region (@code{kill-region}).
191 @item M-w
192 Copy the region into the kill ring (@code{kill-ring-save}).
193 @item M-d
194 Kill the next word (@code{kill-word}). @xref{Words}.
195 @item M-@key{DEL}
196 Kill one word backwards (@code{backward-kill-word}).
197 @item C-x @key{DEL}
198 Kill back to beginning of sentence (@code{backward-kill-sentence}).
199 @xref{Sentences}.
200 @item M-k
201 Kill to the end of the sentence (@code{kill-sentence}).
202 @item C-M-k
203 Kill the following balanced expression (@code{kill-sexp}). @xref{Expressions}.
204 @item M-z @var{char}
205 Kill through the next occurrence of @var{char} (@code{zap-to-char}).
206 @end table
207
208 @kindex C-w
209 @findex kill-region
210 @kindex M-w
211 @findex kill-ring-save
212 One of the commonly-used kill commands is @kbd{C-w}
213 (@code{kill-region}), which kills the text in the region
214 (@pxref{Mark}). Similarly, @kbd{M-w} (@code{kill-ring-save}) copies
215 the text in the region into the kill ring without removing it from the
216 buffer. If the mark is inactive when you type @kbd{C-w} or @kbd{M-w},
217 the command acts on the text between point and where you last set the
218 mark (@pxref{Using Region}).
219
220 Emacs also provides commands to kill specific syntactic units:
221 words, with @kbd{M-@key{DEL}} and @kbd{M-d} (@pxref{Words}); balanced
222 expressions, with @kbd{C-M-k} (@pxref{Expressions}); and sentences,
223 with @kbd{C-x @key{DEL}} and @kbd{M-k} (@pxref{Sentences}).
224
225 @kindex M-z
226 @findex zap-to-char
227 The command @kbd{M-z} (@code{zap-to-char}) combines killing with
228 searching: it reads a character and kills from point up to (and
229 including) the next occurrence of that character in the buffer. A
230 numeric argument acts as a repeat count; a negative argument means to
231 search backward and kill text before point.
232
233 @node Kill Options
234 @subsection Options for Killing
235
236 @vindex kill-read-only-ok
237 @cindex read-only text, killing
238 Some specialized buffers contain @dfn{read-only text}, which cannot
239 be modified and therefore cannot be killed. The kill commands work
240 specially in a read-only buffer: they move over text and copy it to
241 the kill ring, without actually deleting it from the buffer.
242 Normally, they also beep and display an error message when this
243 happens. But if you set the variable @code{kill-read-only-ok} to a
244 non-@code{nil} value, they just print a message in the echo area to
245 explain why the text has not been erased.
246
247 @vindex kill-do-not-save-duplicates
248 If you change the variable @code{kill-do-not-save-duplicates} to a
249 non-@code{nil} value, identical subsequent kills yield a single
250 kill-ring entry, without duplication.
251
252 @node Yanking
253 @section Yanking
254 @cindex moving text
255 @cindex copying text
256 @cindex kill ring
257 @cindex yanking
258 @cindex pasting
259
260 @dfn{Yanking} means reinserting text previously killed. The usual
261 way to move or copy text is to kill it and then yank it elsewhere.
262
263 @table @kbd
264 @item C-y
265 Yank the last kill into the buffer, at point (@code{yank}).
266 @item M-y
267 Replace the text just yanked with an earlier batch of killed text
268 (@code{yank-pop}). @xref{Earlier Kills}.
269 @item C-M-w
270 Cause the following command, if it is a kill command, to append to the
271 previous kill (@code{append-next-kill}). @xref{Appending Kills}.
272 @end table
273
274 @kindex C-y
275 @findex yank
276 The basic yanking command is @kbd{C-y} (@code{yank}). It inserts
277 the most recent kill, leaving the cursor at the end of the inserted
278 text. It also sets the mark at the beginning of the inserted text,
279 without activating the mark; this lets you jump easily to that
280 position, if you wish, with @kbd{C-u C-@key{SPC}} (@pxref{Mark Ring}).
281
282 With a plain prefix argument (@kbd{C-u C-y}), the command instead
283 leaves the cursor in front of the inserted text, and sets the mark at
284 the end. Using any other prefix argument specifies an earlier kill;
285 e.g. @kbd{C-u 4 C-y} reinserts the fourth most recent kill.
286 @xref{Earlier Kills}.
287
288 On graphical displays, @kbd{C-y} first checks if another application
289 has placed any text in the system clipboard more recently than the
290 last Emacs kill. If so, it inserts the text in the clipboard instead.
291 Thus, Emacs effectively treats ``cut'' or ``copy'' clipboard
292 operations performed in other applications like Emacs kills, except
293 that they are not recorded in the kill ring. @xref{Cut and Paste},
294 for details.
295
296 @menu
297 * Kill Ring:: Where killed text is stored.
298 * Earlier Kills:: Yanking something killed some time ago.
299 * Appending Kills:: Several kills in a row all yank together.
300 @end menu
301
302 @node Kill Ring
303 @subsection The Kill Ring
304
305 The @dfn{kill ring} is a list of blocks of text that were previously
306 killed. There is only one kill ring, shared by all buffers, so you
307 can kill text in one buffer and yank it in another buffer. This is
308 the usual way to move text from one buffer to another. (There are
309 several other methods: for instance, you could store the text in a
310 register; see @ref{Registers}. @xref{Accumulating Text}, for some
311 other ways to move text around.)
312
313 @vindex kill-ring-max
314 The maximum number of entries in the kill ring is controlled by the
315 variable @code{kill-ring-max}. The default is 60. If you make a new
316 kill when this limit has been reached, Emacs makes room by deleting
317 the oldest entry in the kill ring.
318
319 @vindex kill-ring
320 The actual contents of the kill ring are stored in a variable named
321 @code{kill-ring}; you can view the entire contents of the kill ring
322 with @kbd{C-h v kill-ring}.
323
324 @node Earlier Kills
325 @subsection Yanking Earlier Kills
326 @cindex yanking previous kills
327
328 As explained in @ref{Yanking}, you can use a numeric argument to
329 @kbd{C-y} to yank text that is no longer the most recent kill. This
330 is useful if you remember which kill ring entry you want. If you
331 don't, you can use the @kbd{M-y} (@code{yank-pop}) command to cycle
332 through the possibilities.
333
334 @kindex M-y
335 @findex yank-pop
336 If the previous command was a yank command, @kbd{M-y} takes the text
337 that was yanked and replaces it with the text from an earlier kill.
338 So, to recover the text of the next-to-the-last kill, first use
339 @kbd{C-y} to yank the last kill, and then use @kbd{M-y} to replace it
340 with the previous kill. @kbd{M-y} is allowed only after a @kbd{C-y}
341 or another @kbd{M-y}.
342
343 You can understand @kbd{M-y} in terms of a ``last yank'' pointer which
344 points at an entry in the kill ring. Each time you kill, the ``last
345 yank'' pointer moves to the newly made entry at the front of the ring.
346 @kbd{C-y} yanks the entry which the ``last yank'' pointer points to.
347 @kbd{M-y} moves the ``last yank'' pointer to a different entry, and the
348 text in the buffer changes to match. Enough @kbd{M-y} commands can move
349 the pointer to any entry in the ring, so you can get any entry into the
350 buffer. Eventually the pointer reaches the end of the ring; the next
351 @kbd{M-y} loops back around to the first entry again.
352
353 @kbd{M-y} moves the ``last yank'' pointer around the ring, but it does
354 not change the order of the entries in the ring, which always runs from
355 the most recent kill at the front to the oldest one still remembered.
356
357 @kbd{M-y} can take a numeric argument, which tells it how many entries
358 to advance the ``last yank'' pointer by. A negative argument moves the
359 pointer toward the front of the ring; from the front of the ring, it
360 moves ``around'' to the last entry and continues forward from there.
361
362 Once the text you are looking for is brought into the buffer, you can
363 stop doing @kbd{M-y} commands and it will stay there. It's just a copy
364 of the kill ring entry, so editing it in the buffer does not change
365 what's in the ring. As long as no new killing is done, the ``last
366 yank'' pointer remains at the same place in the kill ring, so repeating
367 @kbd{C-y} will yank another copy of the same previous kill.
368
369 When you call @kbd{C-y} with a numeric argument, that also sets the
370 ``last yank'' pointer to the entry that it yanks.
371
372 @node Appending Kills
373 @subsection Appending Kills
374
375 @cindex appending kills in the ring
376 Normally, each kill command pushes a new entry onto the kill ring.
377 However, two or more kill commands in a row combine their text into a
378 single entry, so that a single @kbd{C-y} yanks all the text as a unit,
379 just as it was before it was killed.
380
381 Thus, if you want to yank text as a unit, you need not kill all of it
382 with one command; you can keep killing line after line, or word after
383 word, until you have killed it all, and you can still get it all back at
384 once.
385
386 Commands that kill forward from point add onto the end of the previous
387 killed text. Commands that kill backward from point add text onto the
388 beginning. This way, any sequence of mixed forward and backward kill
389 commands puts all the killed text into one entry without rearrangement.
390 Numeric arguments do not break the sequence of appending kills. For
391 example, suppose the buffer contains this text:
392
393 @example
394 This is a line @point{}of sample text.
395 @end example
396
397 @noindent
398 with point shown by @point{}. If you type @kbd{M-d M-@key{DEL} M-d
399 M-@key{DEL}}, killing alternately forward and backward, you end up with
400 @samp{a line of sample} as one entry in the kill ring, and @samp{This
401 is@ @ text.} in the buffer. (Note the double space between @samp{is}
402 and @samp{text}, which you can clean up with @kbd{M-@key{SPC}} or
403 @kbd{M-q}.)
404
405 Another way to kill the same text is to move back two words with
406 @kbd{M-b M-b}, then kill all four words forward with @kbd{C-u M-d}.
407 This produces exactly the same results in the buffer and in the kill
408 ring. @kbd{M-f M-f C-u M-@key{DEL}} kills the same text, all going
409 backward; once again, the result is the same. The text in the kill ring
410 entry always has the same order that it had in the buffer before you
411 killed it.
412
413 @kindex C-M-w
414 @findex append-next-kill
415 If a kill command is separated from the last kill command by other
416 commands (not just numeric arguments), it starts a new entry on the kill
417 ring. But you can force it to append by first typing the command
418 @kbd{C-M-w} (@code{append-next-kill}) right before it. The @kbd{C-M-w}
419 tells the following command, if it is a kill command, to append the text
420 it kills to the last killed text, instead of starting a new entry. With
421 @kbd{C-M-w}, you can kill several separated pieces of text and
422 accumulate them to be yanked back in one place.@refill
423
424 A kill command following @kbd{M-w} (@code{kill-ring-save}) does not
425 append to the text that @kbd{M-w} copied into the kill ring.
426
427 @node Cut and Paste
428 @section ``Cut and Paste'' Operations on Graphical Displays
429 @cindex cut
430 @cindex copy
431 @cindex paste
432
433 In most graphical desktop environments, you can transfer data
434 (usually text) between different applications using a system facility
435 called the @dfn{clipboard}. On X, two other similar facilities are
436 available: the primary selection and the secondary selection. When
437 Emacs is run on a graphical display, its kill and yank commands
438 integrate with these facilities, so that you can easily transfer text
439 between Emacs and other graphical applications.
440
441 By default, Emacs uses UTF-8 as the coding system for inter-program
442 text transfers. If you find that the pasted text is not what you
443 expected, you can specify another coding system by typing @kbd{C-x
444 @key{RET} x} or @kbd{C-x @key{RET} X}. You can also request a
445 different data type by customizing @code{x-select-request-type}.
446 @xref{Communication Coding}.
447
448 @menu
449 * Clipboard:: How Emacs uses the system clipboard.
450 * Primary Selection:: The temporarily selected text selection.
451 * Secondary Selection:: Cutting without altering point and mark.
452 @end menu
453
454 @node Clipboard
455 @subsection Using the Clipboard
456 @cindex clipboard
457
458 The @dfn{clipboard} is the facility that most graphical applications
459 use for ``cutting and pasting''. When the clipboard exists, the kill
460 and yank commands in Emacs make use of it.
461
462 When you kill some text with a command such as @kbd{C-w}
463 (@code{kill-region}), or copy it to the kill ring with a command such
464 as @kbd{M-w} (@code{kill-ring-save}), that text is also put in the
465 clipboard.
466
467 @vindex save-interprogram-paste-before-kill
468 When an Emacs kill command puts text in the clipboard, the existing
469 clipboard contents are normally lost. Optionally, you can change
470 @code{save-interprogram-paste-before-kill} to @code{t}. Then Emacs
471 will first save the clipboard to its kill ring, preventing you from
472 losing the old clipboard data---at the risk of high memory consumption
473 if that data turns out to be large.
474
475 Yank commands, such as @kbd{C-y} (@code{yank}), also use the
476 clipboard. If another application ``owns'' the clipboard---i.e., if
477 you cut or copied text there more recently than your last kill command
478 in Emacs---then Emacs yanks from the clipboard instead of the kill
479 ring.
480
481 @vindex yank-pop-change-selection
482 Normally, rotating the kill ring with @kbd{M-y} (@code{yank-pop})
483 does not alter the clipboard. However, if you change
484 @code{yank-pop-change-selection} to @code{t}, then @kbd{M-y} saves the
485 new yank to the clipboard.
486
487 @vindex x-select-enable-clipboard
488 To prevent kill and yank commands from accessing the clipboard,
489 change the variable @code{x-select-enable-clipboard} to @code{nil}.
490
491 @vindex x-select-enable-primary
492 @findex clipboard-kill-region
493 @findex clipboard-kill-ring-save
494 @findex clipboard-yank
495 Prior to Emacs 24, the kill and yank commands used the primary
496 selection (@pxref{Primary Selection}), not the clipboard. If you
497 prefer this behavior, change @code{x-select-enable-clipboard} to
498 @code{nil}, @code{x-select-enable-primary} to @code{t}, and
499 @code{mouse-drag-copy-region} to @code{t}. In this case, you can use
500 the following commands to act explicitly on the clipboard:
501 @code{clipboard-kill-region} kills the region and saves it to the
502 clipboard; @code{clipboard-kill-ring-save} copies the region to the
503 kill ring and saves it to the clipboard; and @code{clipboard-yank}
504 yanks the contents of the clipboard at point.
505
506 @node Primary Selection
507 @subsection Cut and Paste with Other Window Applications
508 @cindex X cutting and pasting
509 @cindex X selection
510 @cindex primary selection
511 @cindex selection, primary
512
513 Under the X Window System, there exists a @dfn{primary selection}
514 containing the last stretch of text selected in an X application
515 (usually by dragging the mouse). Typically, this text can be inserted
516 into other X applications by @kbd{mouse-2} clicks. The primary
517 selection is separate from the clipboard. Its contents are more
518 ``fragile''; they are overwritten each time you select text with the
519 mouse, whereas the clipboard is only overwritten by explicit ``cut''
520 or ``copy'' commands.
521
522 Under X, whenever the region is active (@pxref{Mark}), the text in
523 the region is saved in the primary selection. This applies regardless
524 of whether the region was made by dragging or clicking the mouse
525 (@pxref{Mouse Commands}), or by keyboard commands (e.g. by typing
526 @kbd{C-@key{SPC}} and moving point; @pxref{Setting Mark}).
527
528 @vindex select-active-regions
529 If you change the variable @code{select-active-regions} to
530 @code{only}, Emacs saves only temporarily active regions to the
531 primary selection, i.e. those made with the mouse or with shift
532 selection (@pxref{Shift Selection}). If you change
533 @code{select-active-regions} to @code{nil}, Emacs avoids saving active
534 regions to the primary selection entirely.
535
536 To insert the primary selection into an Emacs buffer, click
537 @kbd{mouse-2} (@code{mouse-yank-primary}) where you want to insert it.
538 @xref{Mouse Commands}.
539
540 @cindex MS-Windows, and primary selection
541 MS-Windows provides no primary selection, but Emacs emulates it
542 within a single Emacs session by storing the selected text internally.
543 Therefore, all the features and commands related to the primary
544 selection work on Windows as they do on X, for cutting and pasting
545 within the same session, but not across Emacs sessions or with other
546 applications.
547
548 @node Secondary Selection
549 @subsection Secondary Selection
550 @cindex secondary selection
551
552 In addition to the primary selection, the X Window System provides a
553 second similar facility known as the @dfn{secondary selection}.
554 Nowadays, few X applications make use of the secondary selection, but
555 you can access it using the following Emacs commands:
556
557 @table @kbd
558 @findex mouse-set-secondary
559 @kindex M-Drag-Mouse-1
560 @item M-Drag-Mouse-1
561 Set the secondary selection, with one end at the place where you press
562 down the button, and the other end at the place where you release it
563 (@code{mouse-set-secondary}). The selected text is highlighted, using
564 the @code{secondary-selection} face, as you drag. The window scrolls
565 automatically if you drag the mouse off the top or bottom of the
566 window, just like @code{mouse-set-region} (@pxref{Mouse Commands}).
567
568 This command does not alter the kill ring.
569
570 @findex mouse-start-secondary
571 @kindex M-Mouse-1
572 @item M-Mouse-1
573 Set one endpoint for the @dfn{secondary selection}
574 (@code{mouse-start-secondary}).
575
576 @findex mouse-secondary-save-then-kill
577 @kindex M-Mouse-3
578 @item M-Mouse-3
579 Set the secondary selection, with one end at the position clicked and
580 the other at the position specified with @kbd{M-Mouse-1}
581 (@code{mouse-secondary-save-then-kill}). This also puts the selected
582 text in the kill ring. A second @kbd{M-Mouse-3} at the same place
583 kills the secondary selection just made.
584
585 @findex mouse-yank-secondary
586 @kindex M-Mouse-2
587 @item M-Mouse-2
588 Insert the secondary selection where you click, placing point at the
589 end of the yanked text (@code{mouse-yank-secondary}).
590 @end table
591
592 Double or triple clicking of @kbd{M-Mouse-1} operates on words and
593 lines, much like @kbd{Mouse-1}.
594
595 If @code{mouse-yank-at-point} is non-@code{nil}, @kbd{M-Mouse-2} yanks
596 at point. Then it does not matter precisely where you click, or even
597 which of the frame's windows you click on. @xref{Mouse Commands}.
598
599 @node Accumulating Text
600 @section Accumulating Text
601 @findex append-to-buffer
602 @findex prepend-to-buffer
603 @findex copy-to-buffer
604 @findex append-to-file
605
606 @cindex accumulating scattered text
607 Usually we copy or move text by killing it and yanking it, but there
608 are other convenient methods for copying one block of text in many
609 places, or for copying many scattered blocks of text into one place.
610 Here we describe the commands to accumulate scattered pieces of text
611 into a buffer or into a file.
612
613 @table @kbd
614 @item M-x append-to-buffer
615 Append region to the contents of a specified buffer.
616 @item M-x prepend-to-buffer
617 Prepend region to the contents of a specified buffer.
618 @item M-x copy-to-buffer
619 Copy region into a specified buffer, deleting that buffer's old contents.
620 @item M-x insert-buffer
621 Insert the contents of a specified buffer into current buffer at point.
622 @item M-x append-to-file
623 Append region to the contents of a specified file, at the end.
624 @end table
625
626 To accumulate text into a buffer, use @kbd{M-x append-to-buffer}.
627 This reads a buffer name, then inserts a copy of the region into the
628 buffer specified. If you specify a nonexistent buffer,
629 @code{append-to-buffer} creates the buffer. The text is inserted
630 wherever point is in that buffer. If you have been using the buffer for
631 editing, the copied text goes into the middle of the text of the buffer,
632 starting from wherever point happens to be at that moment.
633
634 Point in that buffer is left at the end of the copied text, so
635 successive uses of @code{append-to-buffer} accumulate the text in the
636 specified buffer in the same order as they were copied. Strictly
637 speaking, @code{append-to-buffer} does not always append to the text
638 already in the buffer---it appends only if point in that buffer is at
639 the end. However, if @code{append-to-buffer} is the only command you
640 use to alter a buffer, then point is always at the end.
641
642 @kbd{M-x prepend-to-buffer} is just like @code{append-to-buffer}
643 except that point in the other buffer is left before the copied text, so
644 successive prependings add text in reverse order. @kbd{M-x
645 copy-to-buffer} is similar, except that any existing text in the other
646 buffer is deleted, so the buffer is left containing just the text newly
647 copied into it.
648
649 The command @kbd{M-x insert-buffer} can be used to retrieve the
650 accumulated text from another buffer. This prompts for the name of a
651 buffer, and inserts a copy of all the text in that buffer into the
652 current buffer at point, leaving point at the beginning of the
653 inserted text. It also adds the position of the end of the inserted
654 text to the mark ring, without activating the mark. @xref{Buffers},
655 for background information on buffers.
656
657 Instead of accumulating text in a buffer, you can append text
658 directly into a file with @kbd{M-x append-to-file}. This prompts for
659 a filename, and adds the text of the region to the end of the
660 specified file. The file is changed immediately on disk.
661
662 You should use @code{append-to-file} only with files that are
663 @emph{not} being visited in Emacs. Using it on a file that you are
664 editing in Emacs would change the file behind Emacs's back, which
665 can lead to losing some of your editing.
666
667 Another way to move text around is to store it in a register.
668 @xref{Registers}.
669
670 @node Rectangles
671 @section Rectangles
672 @cindex rectangle
673 @cindex columns (and rectangles)
674 @cindex killing rectangular areas of text
675
676 @dfn{Rectangle} commands operate on rectangular areas of the text:
677 all the characters between a certain pair of columns, in a certain
678 range of lines. Emacs has commands to kill rectangles, yank killed
679 rectangles, clear them out, fill them with blanks or text, or delete
680 them. Rectangle commands are useful with text in multicolumn formats,
681 and for changing text into or out of such formats.
682
683 @cindex mark rectangle
684 To specify a rectangle for a command to work on, set the mark at one
685 corner and point at the opposite corner. The rectangle thus specified
686 is called the @dfn{region-rectangle}. If point and the mark are in
687 the same column, the region-rectangle is empty. If they are in the
688 same line, the region-rectangle is one line high.
689
690 The region-rectangle is controlled in much the same way as the
691 region is controlled. But remember that a given combination of point
692 and mark values can be interpreted either as a region or as a
693 rectangle, depending on the command that uses them.
694
695 @table @kbd
696 @item C-x r k
697 Kill the text of the region-rectangle, saving its contents as the
698 ``last killed rectangle'' (@code{kill-rectangle}).
699 @item C-x r d
700 Delete the text of the region-rectangle (@code{delete-rectangle}).
701 @item C-x r y
702 Yank the last killed rectangle with its upper left corner at point
703 (@code{yank-rectangle}).
704 @item C-x r o
705 Insert blank space to fill the space of the region-rectangle
706 (@code{open-rectangle}). This pushes the previous contents of the
707 region-rectangle to the right.
708 @item C-x r N
709 Insert line numbers along the left edge of the region-rectangle
710 (@code{rectangle-number-lines}). This pushes the previous contents of
711 the region-rectangle to the right.
712 @item C-x r c
713 Clear the region-rectangle by replacing all of its contents with spaces
714 (@code{clear-rectangle}).
715 @item M-x delete-whitespace-rectangle
716 Delete whitespace in each of the lines on the specified rectangle,
717 starting from the left edge column of the rectangle.
718 @item C-x r t @var{string} @key{RET}
719 Replace rectangle contents with @var{string} on each line
720 (@code{string-rectangle}).
721 @item M-x string-insert-rectangle @key{RET} @var{string} @key{RET}
722 Insert @var{string} on each line of the rectangle.
723 @end table
724
725 The rectangle operations fall into two classes: commands to erase or
726 insert rectangles, and commands to make blank rectangles.
727
728 @kindex C-x r k
729 @kindex C-x r d
730 @findex kill-rectangle
731 @findex delete-rectangle
732 There are two ways to erase the text in a rectangle: @kbd{C-x r d}
733 (@code{delete-rectangle}) to delete the text outright, or @kbd{C-x r
734 k} (@code{kill-rectangle}) to remove the text and and save it as the
735 @dfn{last killed rectangle}. In both cases, erasing the
736 region-rectangle is like erasing the specified text on each line of
737 the rectange; if there is any following text on the line, it moves
738 backwards to fill the gap.
739
740 ``Killing'' a rectangle is not killing in the usual sense; the
741 rectangle is not stored in the kill ring, but in a special place that
742 only records the most recent rectangle killed. This is because
743 yanking a rectangle is so different from yanking linear text that
744 different yank commands have to be used. Yank-popping is not defined
745 for rectangles.
746
747 @kindex C-x r y
748 @findex yank-rectangle
749 To yank the last killed rectangle, type @kbd{C-x r y}
750 (@code{yank-rectangle}). The rectangle's first line is inserted at
751 point, the rectangle's second line is inserted at the same horizontal
752 position one line vertically below, and so on. The number of lines
753 affected is determined by the height of the saved rectangle.
754
755 For example, you can convert two single-column lists into a
756 double-column list by killing one of the single-column lists as a
757 rectangle, and then yanking it beside the other list.
758
759 You can also copy rectangles into and out of registers with @kbd{C-x r
760 r @var{r}} and @kbd{C-x r i @var{r}}. @xref{Rectangle Registers}.
761
762 @kindex C-x r o
763 @findex open-rectangle
764 @kindex C-x r c
765 @findex clear-rectangle
766 There are two commands you can use for making blank rectangles:
767 @kbd{C-x r c} (@code{clear-rectangle}) blanks out existing text in the
768 region-rectangle, and @kbd{C-x r o} (@code{open-rectangle}) inserts a
769 blank rectangle.
770
771 @findex delete-whitespace-rectangle
772 @kbd{M-x delete-whitespace-rectangle} deletes horizontal whitespace
773 starting from a particular column. This applies to each of the lines
774 in the rectangle, and the column is specified by the left edge of the
775 rectangle. The right edge of the rectangle does not make any
776 difference to this command.
777
778 @kindex C-x r N
779 @findex rectangle
780 The command @kbd{C-x r N} (@code{rectangle-number-lines}) inserts
781 line numbers along the left edge of the region-rectangle. Normally,
782 the numbering begins from 1 (for the first line of the rectangle).
783 With a prefix argument, the command prompts for a number to begin
784 from, and for a format string with which to print the numbers
785 (@pxref{Formatting Strings,,, elisp, The Emacs Lisp Reference
786 Manual}).
787
788 @kindex C-x r t
789 @findex string-rectangle
790 The command @kbd{C-x r t} (@code{string-rectangle}) replaces the
791 contents of a region-rectangle with a string on each line. The
792 string's width need not be the same as the width of the rectangle. If
793 the string's width is less, the text after the rectangle shifts left;
794 if the string is wider than the rectangle, the text after the
795 rectangle shifts right.
796
797 @findex string-insert-rectangle
798 The command @kbd{M-x string-insert-rectangle} is similar to
799 @code{string-rectangle}, but inserts the string on each line,
800 shifting the original text to the right.
801
802 @node CUA Bindings
803 @section CUA Bindings
804 @findex cua-mode
805 @vindex cua-mode
806 @cindex CUA key bindings
807 @vindex cua-enable-cua-keys
808 The command @kbd{M-x cua-mode} sets up key bindings that are
809 compatible with the Common User Access (CUA) system used in many other
810 applications.
811
812 When CUA mode is enabled, the keys @kbd{C-x}, @kbd{C-c}, @kbd{C-v},
813 and @kbd{C-z} invoke commands that cut (kill), copy, paste (yank), and
814 undo respectively. The @kbd{C-x} and @kbd{C-c} keys perform cut and
815 copy only if the region is active. Otherwise, they still act as
816 prefix keys, so that standard Emacs commands like @kbd{C-x C-c} still
817 work. Note that this means the variable @code{mark-even-if-inactive}
818 has no effect for @kbd{C-x} and @kbd{C-c} (@pxref{Using Region}).
819
820 To enter an Emacs command like @kbd{C-x C-f} while the mark is
821 active, use one of the following methods: either hold @kbd{Shift}
822 together with the prefix key, e.g. @kbd{S-C-x C-f}, or quickly type
823 the prefix key twice, e.g. @kbd{C-x C-x C-f}.
824
825 To disable the overriding of standard Emacs binding by CUA mode,
826 while retaining the other features of CUA mode described below, set
827 the variable @code{cua-enable-cua-keys} to @code{nil}.
828
829 In CUA mode, typed text replaces the active region as in
830 Delete-Selection mode (@pxref{Mouse Commands}).
831
832 @cindex rectangle highlighting
833 CUA mode provides enhanced rectangle support with visible
834 rectangle highlighting. Use @kbd{C-RET} to start a rectangle,
835 extend it using the movement commands, and cut or copy it using
836 @kbd{C-x} or @kbd{C-c}. @kbd{RET} moves the cursor to the next
837 (clockwise) corner of the rectangle, so you can easily expand it in
838 any direction. Normal text you type is inserted to the left or right
839 of each line in the rectangle (on the same side as the cursor).
840
841 With CUA you can easily copy text and rectangles into and out of
842 registers by providing a one-digit numeric prefix to the kill, copy,
843 and yank commands, e.g. @kbd{C-1 C-c} copies the region into register
844 @code{1}, and @kbd{C-2 C-v} yanks the contents of register @code{2}.
845
846 @cindex global mark
847 CUA mode also has a global mark feature which allows easy moving and
848 copying of text between buffers. Use @kbd{C-S-SPC} to toggle the
849 global mark on and off. When the global mark is on, all text that you
850 kill or copy is automatically inserted at the global mark, and text
851 you type is inserted at the global mark rather than at the current
852 position.
853
854 For example, to copy words from various buffers into a word list in
855 a given buffer, set the global mark in the target buffer, then
856 navigate to each of the words you want in the list, mark it (e.g. with
857 @kbd{S-M-f}), copy it to the list with @kbd{C-c} or @kbd{M-w}, and
858 insert a newline after the word in the target list by pressing
859 @key{RET}.