Commit | Line | Data |
---|---|---|
6bf7aab6 | 1 | @c This is part of the Emacs manual. |
d621caf7 | 2 | @c Copyright (C) 1985,86,87,93,94,95,97,2000 Free Software Foundation, Inc. |
6bf7aab6 DL |
3 | @c See file emacs.texi for copying conditions. |
4 | @iftex | |
5 | @chapter Killing and Moving Text | |
6 | ||
7 | @dfn{Killing} means erasing text and copying it into the @dfn{kill | |
8 | ring}, from which it can be retrieved by @dfn{yanking} it. Some systems | |
9 | use the terms ``cutting'' and ``pasting'' for these operations. | |
10 | ||
11 | The commonest way of moving or copying text within Emacs is to kill it | |
12 | and later yank it elsewhere in one or more places. This is very safe | |
13 | because Emacs remembers several recent kills, not just the last one. It | |
14 | is versatile, because the many commands for killing syntactic units can | |
15 | also be used for moving those units. But there are other ways of | |
16 | copying text for special purposes. | |
17 | ||
18 | Emacs has only one kill ring for all buffers, so you can kill text in | |
19 | one buffer and yank it in another buffer. | |
20 | ||
21 | @end iftex | |
22 | ||
23 | @node Killing, Yanking, Mark, Top | |
24 | @section Deletion and Killing | |
25 | ||
26 | @cindex killing text | |
27 | @cindex cutting text | |
28 | @cindex deletion | |
29 | Most commands which erase text from the buffer save it in the kill | |
30 | ring so that you can move or copy it to other parts of the buffer. | |
31 | These commands are known as @dfn{kill} commands. The rest of the | |
32 | commands that erase text do not save it in the kill ring; they are known | |
33 | as @dfn{delete} commands. (This distinction is made only for erasure of | |
34 | text in the buffer.) If you do a kill or delete command by mistake, you | |
35 | can use the @kbd{C-x u} (@code{undo}) command to undo it | |
36 | (@pxref{Undo}). | |
37 | ||
8c1d7d60 EZ |
38 | @vindex kill-read-only-ok |
39 | @cindex read-only text, killing | |
40 | By default, Emacs does not allow to kill text in read-only buffers. | |
41 | Setting the variable @code{kill-read-only-ok} to a non-@code{nil} value | |
42 | overrides that. To alert you to the fact that you killed read-only | |
43 | text, Emacs prints a message to that effect in the echo area. | |
44 | ||
6bf7aab6 DL |
45 | The delete commands include @kbd{C-d} (@code{delete-char}) and |
46 | @key{DEL} (@code{delete-backward-char}), which delete only one character at | |
47 | a time, and those commands that delete only spaces or newlines. Commands | |
48 | that can destroy significant amounts of nontrivial data generally kill. | |
49 | The commands' names and individual descriptions use the words @samp{kill} | |
50 | and @samp{delete} to say which they do. | |
51 | ||
dd5c1ea9 DL |
52 | @cindex Delete Selection mode |
53 | @cindex mode, Delete Selection | |
54 | @findex delete-selection-mode | |
55 | You can arrange for selected text to be killed when you insert something | |
56 | and replaced by what you insert; this is the way many text interfaces | |
57 | work. To do this turn on Delete Selection mode. with @kbd{M-x | |
58 | delete-selection-mode} or using Custom. Also in Delete Selection mode | |
59 | @key{DEL}, @kbd{C-d} and some other keys will just kill the whole | |
60 | selection and Transient Mark mode is turned on (@pxref{Transient Mark}). | |
61 | ||
6bf7aab6 DL |
62 | @menu |
63 | * Deletion:: Commands for deleting small amounts of text and | |
64 | blank areas. | |
65 | * Killing by Lines:: How to kill entire lines of text at one time. | |
66 | * Other Kill Commands:: Commands to kill large regions of text and | |
67 | syntactic units such as words and sentences. | |
68 | @end menu | |
69 | ||
70 | @node Deletion | |
71 | @subsection Deletion | |
72 | @c ??? Should be backward-delete-char | |
73 | @findex delete-backward-char | |
74 | @findex delete-char | |
75 | @kindex DEL | |
76 | @kindex C-d | |
77 | ||
78 | @table @kbd | |
79 | @item C-d | |
80 | Delete next character (@code{delete-char}). | |
81 | @item @key{DEL} | |
82 | Delete previous character (@code{delete-backward-char}). | |
83 | @item M-\ | |
84 | Delete spaces and tabs around point (@code{delete-horizontal-space}). | |
85 | @item M-@key{SPC} | |
86 | Delete spaces and tabs around point, leaving one space | |
87 | (@code{just-one-space}). | |
88 | @item C-x C-o | |
89 | Delete blank lines around the current line (@code{delete-blank-lines}). | |
90 | @item M-^ | |
91 | Join two lines by deleting the intervening newline, along with any | |
92 | indentation following it (@code{delete-indentation}). | |
93 | @end table | |
94 | ||
95 | The most basic delete commands are @kbd{C-d} (@code{delete-char}) and | |
96 | @key{DEL} (@code{delete-backward-char}). @kbd{C-d} deletes the | |
97 | character after point, the one the cursor is ``on top of.'' This | |
98 | doesn't move point. @key{DEL} deletes the character before the cursor, | |
99 | and moves point back. You can delete newlines like any other characters | |
100 | in the buffer; deleting a newline joins two lines. Actually, @kbd{C-d} | |
101 | and @key{DEL} aren't always delete commands; when given arguments, they | |
102 | kill instead, since they can erase more than one character this way. | |
103 | ||
104 | @kindex M-\ | |
105 | @findex delete-horizontal-space | |
106 | @kindex M-SPC | |
107 | @findex just-one-space | |
108 | The other delete commands are those which delete only whitespace | |
109 | characters: spaces, tabs and newlines. @kbd{M-\} | |
110 | (@code{delete-horizontal-space}) deletes all the spaces and tab | |
111 | characters before and after point. @kbd{M-@key{SPC}} | |
112 | (@code{just-one-space}) does likewise but leaves a single space after | |
113 | point, regardless of the number of spaces that existed previously (even | |
114 | zero). | |
115 | ||
116 | @kbd{C-x C-o} (@code{delete-blank-lines}) deletes all blank lines | |
117 | after the current line. If the current line is blank, it deletes all | |
118 | blank lines preceding the current line as well (leaving one blank line, | |
119 | the current line). | |
120 | ||
121 | @kbd{M-^} (@code{delete-indentation}) joins the current line and the | |
122 | previous line, by deleting a newline and all surrounding spaces, usually | |
123 | leaving a single space. @xref{Indentation,M-^}. | |
124 | ||
125 | @node Killing by Lines | |
126 | @subsection Killing by Lines | |
127 | ||
128 | @table @kbd | |
129 | @item C-k | |
130 | Kill rest of line or one or more lines (@code{kill-line}). | |
131 | @end table | |
132 | ||
133 | @kindex C-k | |
134 | @findex kill-line | |
135 | The simplest kill command is @kbd{C-k}. If given at the beginning of | |
136 | a line, it kills all the text on the line, leaving it blank. When used | |
137 | on a blank line, it kills the whole line including its newline. To kill | |
138 | an entire non-blank line, go to the beginning and type @kbd{C-k} twice. | |
139 | ||
140 | More generally, @kbd{C-k} kills from point up to the end of the line, | |
141 | unless it is at the end of a line. In that case it kills the newline | |
142 | following point, thus merging the next line into the current one. | |
143 | Spaces and tabs that you can't see at the end of the line are ignored | |
144 | when deciding which case applies, so if point appears to be at the end | |
145 | of the line, you can be sure @kbd{C-k} will kill the newline. | |
146 | ||
147 | When @kbd{C-k} is given a positive argument, it kills that many lines | |
148 | and the newlines that follow them (however, text on the current line | |
149 | before point is spared). With a negative argument @minus{}@var{n}, it | |
150 | kills @var{n} lines preceding the current line (together with the text | |
151 | on the current line before point). Thus, @kbd{C-u - 2 C-k} at the front | |
152 | of a line kills the two previous lines. | |
153 | ||
154 | @kbd{C-k} with an argument of zero kills the text before point on the | |
155 | current line. | |
156 | ||
157 | @vindex kill-whole-line | |
158 | If the variable @code{kill-whole-line} is non-@code{nil}, @kbd{C-k} at | |
159 | the very beginning of a line kills the entire line including the | |
160 | following newline. This variable is normally @code{nil}. | |
161 | ||
162 | @node Other Kill Commands | |
163 | @subsection Other Kill Commands | |
164 | @findex kill-region | |
165 | @kindex C-w | |
166 | ||
167 | @c DoubleWideCommands | |
168 | @table @kbd | |
169 | @item C-w | |
170 | Kill region (from point to the mark) (@code{kill-region}). | |
171 | @item M-d | |
172 | Kill word (@code{kill-word}). @xref{Words}. | |
173 | @item M-@key{DEL} | |
174 | Kill word backwards (@code{backward-kill-word}). | |
175 | @item C-x @key{DEL} | |
176 | Kill back to beginning of sentence (@code{backward-kill-sentence}). | |
177 | @xref{Sentences}. | |
178 | @item M-k | |
179 | Kill to end of sentence (@code{kill-sentence}). | |
180 | @item C-M-k | |
181 | Kill sexp (@code{kill-sexp}). @xref{Lists}. | |
182 | @item M-z @var{char} | |
183 | Kill through the next occurrence of @var{char} (@code{zap-to-char}). | |
184 | @end table | |
185 | ||
186 | A kill command which is very general is @kbd{C-w} | |
187 | (@code{kill-region}), which kills everything between point and the | |
188 | mark. With this command, you can kill any contiguous sequence of | |
189 | characters, if you first set the region around them. | |
190 | ||
191 | @kindex M-z | |
192 | @findex zap-to-char | |
193 | A convenient way of killing is combined with searching: @kbd{M-z} | |
194 | (@code{zap-to-char}) reads a character and kills from point up to (and | |
195 | including) the next occurrence of that character in the buffer. A | |
196 | numeric argument acts as a repeat count. A negative argument means to | |
197 | search backward and kill text before point. | |
198 | ||
199 | Other syntactic units can be killed: words, with @kbd{M-@key{DEL}} and | |
200 | @kbd{M-d} (@pxref{Words}); sexps, with @kbd{C-M-k} (@pxref{Lists}); and | |
201 | sentences, with @kbd{C-x @key{DEL}} and @kbd{M-k} | |
202 | (@pxref{Sentences}).@refill | |
203 | ||
204 | You can use kill commands in read-only buffers. They don't actually | |
205 | change the buffer, and they beep to warn you of that, but they do copy | |
206 | the text you tried to kill into the kill ring, so you can yank it into | |
207 | other buffers. Most of the kill commands move point across the text | |
208 | they copy in this way, so that successive kill commands build up a | |
209 | single kill ring entry as usual. | |
210 | ||
211 | @node Yanking, Accumulating Text, Killing, Top | |
212 | @section Yanking | |
213 | @cindex moving text | |
214 | @cindex copying text | |
215 | @cindex kill ring | |
216 | @cindex yanking | |
217 | @cindex pasting | |
218 | ||
219 | @dfn{Yanking} means reinserting text previously killed. This is what | |
220 | some systems call ``pasting.'' The usual way to move or copy text is to | |
221 | kill it and then yank it elsewhere one or more times. | |
222 | ||
223 | @table @kbd | |
224 | @item C-y | |
225 | Yank last killed text (@code{yank}). | |
226 | @item M-y | |
227 | Replace text just yanked with an earlier batch of killed text | |
228 | (@code{yank-pop}). | |
229 | @item M-w | |
230 | Save region as last killed text without actually killing it | |
231 | (@code{kill-ring-save}). | |
232 | @item C-M-w | |
233 | Append next kill to last batch of killed text (@code{append-next-kill}). | |
234 | @end table | |
235 | ||
236 | @menu | |
237 | * Kill Ring:: Where killed text is stored. Basic yanking. | |
238 | * Appending Kills:: Several kills in a row all yank together. | |
239 | * Earlier Kills:: Yanking something killed some time ago. | |
240 | @end menu | |
241 | ||
242 | @node Kill Ring | |
243 | @subsection The Kill Ring | |
244 | ||
245 | All killed text is recorded in the @dfn{kill ring}, a list of blocks of | |
246 | text that have been killed. There is only one kill ring, shared by all | |
247 | buffers, so you can kill text in one buffer and yank it in another buffer. | |
248 | This is the usual way to move text from one file to another. | |
249 | (@xref{Accumulating Text}, for some other ways.) | |
250 | ||
251 | @kindex C-y | |
252 | @findex yank | |
253 | The command @kbd{C-y} (@code{yank}) reinserts the text of the most recent | |
254 | kill. It leaves the cursor at the end of the text. It sets the mark at | |
255 | the beginning of the text. @xref{Mark}. | |
256 | ||
257 | @kbd{C-u C-y} leaves the cursor in front of the text, and sets the | |
258 | mark after it. This happens only if the argument is specified with just | |
259 | a @kbd{C-u}, precisely. Any other sort of argument, including @kbd{C-u} | |
260 | and digits, specifies an earlier kill to yank (@pxref{Earlier Kills}). | |
261 | ||
262 | @kindex M-w | |
263 | @findex kill-ring-save | |
264 | To copy a block of text, you can use @kbd{M-w} | |
265 | (@code{kill-ring-save}), which copies the region into the kill ring | |
266 | without removing it from the buffer. This is approximately equivalent | |
267 | to @kbd{C-w} followed by @kbd{C-x u}, except that @kbd{M-w} does not | |
268 | alter the undo history and does not temporarily change the screen. | |
269 | ||
270 | @node Appending Kills | |
271 | @subsection Appending Kills | |
272 | ||
273 | @cindex appending kills in the ring | |
274 | @cindex television | |
275 | Normally, each kill command pushes a new entry onto the kill ring. | |
276 | However, two or more kill commands in a row combine their text into a | |
277 | single entry, so that a single @kbd{C-y} yanks all the text as a unit, | |
278 | just as it was before it was killed. | |
279 | ||
280 | Thus, if you want to yank text as a unit, you need not kill all of it | |
281 | with one command; you can keep killing line after line, or word after | |
282 | word, until you have killed it all, and you can still get it all back at | |
283 | once. | |
284 | ||
285 | Commands that kill forward from point add onto the end of the previous | |
286 | killed text. Commands that kill backward from point add text onto the | |
287 | beginning. This way, any sequence of mixed forward and backward kill | |
288 | commands puts all the killed text into one entry without rearrangement. | |
289 | Numeric arguments do not break the sequence of appending kills. For | |
290 | example, suppose the buffer contains this text: | |
291 | ||
292 | @example | |
293 | This is a line @point{}of sample text. | |
294 | @end example | |
295 | ||
296 | @noindent | |
297 | with point shown by @point{}. If you type @kbd{M-d M-@key{DEL} M-d | |
298 | M-@key{DEL}}, killing alternately forward and backward, you end up with | |
299 | @samp{a line of sample} as one entry in the kill ring, and @samp{This | |
300 | is@ @ text.} in the buffer. (Note the double space, which you can clean | |
301 | up with @kbd{M-@key{SPC}} or @kbd{M-q}.) | |
302 | ||
303 | Another way to kill the same text is to move back two words with | |
304 | @kbd{M-b M-b}, then kill all four words forward with @kbd{C-u M-d}. | |
305 | This produces exactly the same results in the buffer and in the kill | |
306 | ring. @kbd{M-f M-f C-u M-@key{DEL}} kills the same text, all going | |
307 | backward; once again, the result is the same. The text in the kill ring | |
308 | entry always has the same order that it had in the buffer before you | |
309 | killed it. | |
310 | ||
311 | @kindex C-M-w | |
312 | @findex append-next-kill | |
313 | If a kill command is separated from the last kill command by other | |
314 | commands (not just numeric arguments), it starts a new entry on the kill | |
315 | ring. But you can force it to append by first typing the command | |
316 | @kbd{C-M-w} (@code{append-next-kill}) right before it. The @kbd{C-M-w} | |
317 | tells the following command, if it is a kill command, to append the text | |
318 | it kills to the last killed text, instead of starting a new entry. With | |
319 | @kbd{C-M-w}, you can kill several separated pieces of text and | |
320 | accumulate them to be yanked back in one place.@refill | |
321 | ||
322 | A kill command following @kbd{M-w} does not append to the text that | |
323 | @kbd{M-w} copied into the kill ring. | |
324 | ||
325 | @node Earlier Kills | |
326 | @subsection Yanking Earlier Kills | |
327 | ||
328 | @cindex yanking previous kills | |
329 | @kindex M-y | |
330 | @findex yank-pop | |
331 | To recover killed text that is no longer the most recent kill, use the | |
332 | @kbd{M-y} command (@code{yank-pop}). It takes the text previously | |
333 | yanked and replaces it with the text from an earlier kill. So, to | |
334 | recover the text of the next-to-the-last kill, first use @kbd{C-y} to | |
335 | yank the last kill, and then use @kbd{M-y} to replace it with the | |
336 | previous kill. @kbd{M-y} is allowed only after a @kbd{C-y} or another | |
337 | @kbd{M-y}. | |
338 | ||
339 | You can understand @kbd{M-y} in terms of a ``last yank'' pointer which | |
340 | points at an entry in the kill ring. Each time you kill, the ``last | |
341 | yank'' pointer moves to the newly made entry at the front of the ring. | |
342 | @kbd{C-y} yanks the entry which the ``last yank'' pointer points to. | |
343 | @kbd{M-y} moves the ``last yank'' pointer to a different entry, and the | |
344 | text in the buffer changes to match. Enough @kbd{M-y} commands can move | |
345 | the pointer to any entry in the ring, so you can get any entry into the | |
346 | buffer. Eventually the pointer reaches the end of the ring; the next | |
347 | @kbd{M-y} moves it to the first entry again. | |
348 | ||
349 | @kbd{M-y} moves the ``last yank'' pointer around the ring, but it does | |
350 | not change the order of the entries in the ring, which always runs from | |
351 | the most recent kill at the front to the oldest one still remembered. | |
352 | ||
353 | @kbd{M-y} can take a numeric argument, which tells it how many entries | |
354 | to advance the ``last yank'' pointer by. A negative argument moves the | |
355 | pointer toward the front of the ring; from the front of the ring, it | |
356 | moves ``around'' to the last entry and continues forward from there. | |
357 | ||
358 | Once the text you are looking for is brought into the buffer, you can | |
359 | stop doing @kbd{M-y} commands and it will stay there. It's just a copy | |
360 | of the kill ring entry, so editing it in the buffer does not change | |
361 | what's in the ring. As long as no new killing is done, the ``last | |
362 | yank'' pointer remains at the same place in the kill ring, so repeating | |
363 | @kbd{C-y} will yank another copy of the same previous kill. | |
364 | ||
365 | If you know how many @kbd{M-y} commands it would take to find the text | |
366 | you want, you can yank that text in one step using @kbd{C-y} with a | |
367 | numeric argument. @kbd{C-y} with an argument restores the text the | |
368 | specified number of entries back in the kill ring. Thus, @kbd{C-u 2 | |
369 | C-y} gets the next-to-the-last block of killed text. It is equivalent | |
370 | to @kbd{C-y M-y}. @kbd{C-y} with a numeric argument starts counting | |
371 | from the ``last yank'' pointer, and sets the ``last yank'' pointer to | |
372 | the entry that it yanks. | |
373 | ||
374 | @vindex kill-ring-max | |
375 | The length of the kill ring is controlled by the variable | |
376 | @code{kill-ring-max}; no more than that many blocks of killed text are | |
377 | saved. | |
378 | ||
379 | @vindex kill-ring | |
380 | The actual contents of the kill ring are stored in a variable named | |
381 | @code{kill-ring}; you can view the entire contents of the kill ring with | |
382 | the command @kbd{C-h v kill-ring}. | |
383 | ||
384 | @node Accumulating Text, Rectangles, Yanking, Top | |
385 | @section Accumulating Text | |
386 | @findex append-to-buffer | |
387 | @findex prepend-to-buffer | |
388 | @findex copy-to-buffer | |
389 | @findex append-to-file | |
390 | ||
391 | @cindex accumulating scattered text | |
392 | Usually we copy or move text by killing it and yanking it, but there | |
393 | are other methods convenient for copying one block of text in many | |
394 | places, or for copying many scattered blocks of text into one place. To | |
395 | copy one block to many places, store it in a register | |
396 | (@pxref{Registers}). Here we describe the commands to accumulate | |
397 | scattered pieces of text into a buffer or into a file. | |
398 | ||
399 | @table @kbd | |
400 | @item M-x append-to-buffer | |
401 | Append region to contents of specified buffer. | |
402 | @item M-x prepend-to-buffer | |
403 | Prepend region to contents of specified buffer. | |
404 | @item M-x copy-to-buffer | |
405 | Copy region into specified buffer, deleting that buffer's old contents. | |
406 | @item M-x insert-buffer | |
407 | Insert contents of specified buffer into current buffer at point. | |
408 | @item M-x append-to-file | |
409 | Append region to contents of specified file, at the end. | |
410 | @end table | |
411 | ||
412 | To accumulate text into a buffer, use @kbd{M-x append-to-buffer}. | |
413 | This reads a buffer name, then inserts a copy of the region into the | |
414 | buffer specified. If you specify a nonexistent buffer, | |
415 | @code{append-to-buffer} creates the buffer. The text is inserted | |
416 | wherever point is in that buffer. If you have been using the buffer for | |
417 | editing, the copied text goes into the middle of the text of the buffer, | |
418 | wherever point happens to be in it. | |
419 | ||
420 | Point in that buffer is left at the end of the copied text, so | |
421 | successive uses of @code{append-to-buffer} accumulate the text in the | |
422 | specified buffer in the same order as they were copied. Strictly | |
423 | speaking, @code{append-to-buffer} does not always append to the text | |
424 | already in the buffer---it appends only if point in that buffer is at the end. | |
425 | However, if @code{append-to-buffer} is the only command you use to alter | |
426 | a buffer, then point is always at the end. | |
427 | ||
428 | @kbd{M-x prepend-to-buffer} is just like @code{append-to-buffer} | |
429 | except that point in the other buffer is left before the copied text, so | |
430 | successive prependings add text in reverse order. @kbd{M-x | |
431 | copy-to-buffer} is similar except that any existing text in the other | |
432 | buffer is deleted, so the buffer is left containing just the text newly | |
433 | copied into it. | |
434 | ||
435 | To retrieve the accumulated text from another buffer, use the command | |
436 | @kbd{M-x insert-buffer}; this too takes @var{buffername} as an argument. | |
437 | It inserts a copy of the text in buffer @var{buffername} into the | |
438 | selected buffer. You can alternatively select the other buffer for | |
439 | editing, then optionally move text from it by killing. @xref{Buffers}, | |
440 | for background information on buffers. | |
441 | ||
442 | Instead of accumulating text within Emacs, in a buffer, you can append | |
443 | text directly into a file with @kbd{M-x append-to-file}, which takes | |
444 | @var{filename} as an argument. It adds the text of the region to the end | |
445 | of the specified file. The file is changed immediately on disk. | |
446 | ||
447 | You should use @code{append-to-file} only with files that are | |
448 | @emph{not} being visited in Emacs. Using it on a file that you are | |
449 | editing in Emacs would change the file behind Emacs's back, which | |
450 | can lead to losing some of your editing. | |
451 | ||
452 | @node Rectangles, Registers, Accumulating Text, Top | |
453 | @section Rectangles | |
454 | @cindex rectangle | |
455 | @cindex columns (and rectangles) | |
456 | @cindex killing rectangular areas of text | |
457 | ||
458 | The rectangle commands operate on rectangular areas of the text: all | |
459 | the characters between a certain pair of columns, in a certain range of | |
460 | lines. Commands are provided to kill rectangles, yank killed rectangles, | |
461 | clear them out, fill them with blanks or text, or delete them. Rectangle | |
462 | commands are useful with text in multicolumn formats, and for changing | |
463 | text into or out of such formats. | |
464 | ||
465 | When you must specify a rectangle for a command to work on, you do it | |
466 | by putting the mark at one corner and point at the opposite corner. The | |
467 | rectangle thus specified is called the @dfn{region-rectangle} because | |
468 | you control it in about the same way the region is controlled. But | |
469 | remember that a given combination of point and mark values can be | |
470 | interpreted either as a region or as a rectangle, depending on the | |
471 | command that uses them. | |
472 | ||
473 | If point and the mark are in the same column, the rectangle they | |
474 | delimit is empty. If they are in the same line, the rectangle is one | |
475 | line high. This asymmetry between lines and columns comes about | |
476 | because point (and likewise the mark) is between two columns, but within | |
477 | a line. | |
478 | ||
479 | @table @kbd | |
480 | @item C-x r k | |
481 | Kill the text of the region-rectangle, saving its contents as the | |
482 | ``last killed rectangle'' (@code{kill-rectangle}). | |
483 | @item C-x r d | |
484 | Delete the text of the region-rectangle (@code{delete-rectangle}). | |
485 | @item C-x r y | |
486 | Yank the last killed rectangle with its upper left corner at point | |
487 | (@code{yank-rectangle}). | |
488 | @item C-x r o | |
489 | Insert blank space to fill the space of the region-rectangle | |
490 | (@code{open-rectangle}). This pushes the previous contents of the | |
491 | region-rectangle rightward. | |
492 | @item M-x clear-rectangle | |
493 | Clear the region-rectangle by replacing its contents with spaces. | |
494 | @item M-x delete-whitespace-rectangle | |
495 | Delete whitespace in each of the lines on the specified rectangle, | |
496 | starting from the left edge column of the rectangle. | |
d621caf7 | 497 | @item C-x r t @var{string} @key{RET} |
6bf7aab6 DL |
498 | Insert @var{string} on each line of the region-rectangle |
499 | (@code{string-rectangle}). | |
500 | @end table | |
501 | ||
502 | The rectangle operations fall into two classes: commands deleting and | |
503 | inserting rectangles, and commands for blank rectangles. | |
504 | ||
505 | @kindex C-x r k | |
506 | @kindex C-x r d | |
507 | @findex kill-rectangle | |
508 | @findex delete-rectangle | |
509 | There are two ways to get rid of the text in a rectangle: you can | |
510 | discard the text (delete it) or save it as the ``last killed'' | |
511 | rectangle. The commands for these two ways are @kbd{C-x r d} | |
512 | (@code{delete-rectangle}) and @kbd{C-x r k} (@code{kill-rectangle}). In | |
513 | either case, the portion of each line that falls inside the rectangle's | |
514 | boundaries is deleted, causing following text (if any) on the line to | |
515 | move left into the gap. | |
516 | ||
517 | Note that ``killing'' a rectangle is not killing in the usual sense; the | |
518 | rectangle is not stored in the kill ring, but in a special place that | |
519 | can only record the most recent rectangle killed. This is because yanking | |
520 | a rectangle is so different from yanking linear text that different yank | |
521 | commands have to be used and yank-popping is hard to make sense of. | |
522 | ||
523 | @kindex C-x r y | |
524 | @findex yank-rectangle | |
525 | To yank the last killed rectangle, type @kbd{C-x r y} | |
526 | (@code{yank-rectangle}). Yanking a rectangle is the opposite of killing | |
527 | one. Point specifies where to put the rectangle's upper left corner. | |
528 | The rectangle's first line is inserted there, the rectangle's second | |
529 | line is inserted at a position one line vertically down, and so on. The | |
530 | number of lines affected is determined by the height of the saved | |
531 | rectangle. | |
532 | ||
533 | You can convert single-column lists into double-column lists using | |
534 | rectangle killing and yanking; kill the second half of the list as a | |
535 | rectangle and then yank it beside the first line of the list. | |
536 | @xref{Two-Column}, for another way to edit multi-column text. | |
537 | ||
538 | You can also copy rectangles into and out of registers with @kbd{C-x r | |
539 | r @var{r}} and @kbd{C-x r i @var{r}}. @xref{RegRect,,Rectangle | |
540 | Registers}. | |
541 | ||
542 | @kindex C-x r o | |
543 | @findex open-rectangle | |
544 | @findex clear-rectangle | |
545 | There are two commands you can use for making blank rectangles: | |
546 | @kbd{M-x clear-rectangle} which blanks out existing text, and @kbd{C-x r | |
547 | o} (@code{open-rectangle}) which inserts a blank rectangle. Clearing a | |
548 | rectangle is equivalent to deleting it and then inserting a blank | |
549 | rectangle of the same size. | |
550 | ||
551 | @findex delete-whitespace-rectangle | |
552 | The command @kbd{M-x delete-whitespace-rectangle} deletes horizontal | |
553 | whitespace starting from a particular column. This applies to each of | |
554 | the lines in the rectangle, and the column is specified by the left | |
555 | edge of the rectangle. The right edge of the rectangle does not make | |
556 | any difference to this command. | |
557 | ||
558 | @kindex C-x r t | |
559 | @findex string-rectangle | |
560 | The command @kbd{C-x r t} (@code{M-x string-rectangle}) replaces the | |
561 | rectangle with a specified string (inserted once on each line). The | |
562 | string's width need not be the same as the width of the rectangle. If | |
563 | the string's width is less, the text after the rectangle shifts left; if | |
564 | the string is wider than the rectangle, the text after the rectangle | |
565 | shifts right. | |
0309803d DL |
566 | @findex replace-rectangle |
567 | The command @kbd{M-x replace-rectangle} is similar, but replaces the | |
568 | original version. |