annotate man/killing.texi @ 60489:7d03f539a034

Fix last change.
author Kim F. Storm <storm@cua.dk>
date Mon, 07 Mar 2005 13:43:34 +0000
parents c2c2b868b75f
children 45dee811cbe6 3ebd9bdb4fe5
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
1 @c This is part of the Emacs manual.
56899
36c1c98acd4b (Killing): Correct description of kill commands in read-only buffer.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56810
diff changeset
2 @c Copyright (C) 1985,86,87,93,94,95,97,2000,2001,2004
36c1c98acd4b (Killing): Correct description of kill commands in read-only buffer.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56810
diff changeset
3 @c Free Software Foundation, Inc.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
4 @c See file emacs.texi for copying conditions.
59272
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
5
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
6 @node Killing, Yanking, Mark, Top
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
7 @chapter Killing and Moving Text
Dave Love <fx@gnu.org>
parents:
diff changeset
8
56810
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
9 @ifnottex
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
10 @raisesections
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
11 @end ifnottex
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
12
59272
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
13 @dfn{Killing} means erasing text and copying it into the @dfn{kill
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
14 ring}, from which you can bring it back into the buffer by
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
15 @dfn{yanking} it. (Some systems use the terms ``cutting'' and
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
16 ``pasting'' for these operations.) This is the most common way of
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
17 moving or copying text within Emacs. Killing and yanking is very safe
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
18 because Emacs remembers several recent kills, not just the last one.
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
19 It is versatile, because the many commands for killing syntactic units
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
20 can also be used for moving those units. But there are other ways of
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
21 copying text for special purposes.
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
22
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
23 @iftex
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
24 @section Deletion and Killing
59272
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
25 @end iftex
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
26
Dave Love <fx@gnu.org>
parents:
diff changeset
27 @cindex killing text
Dave Love <fx@gnu.org>
parents:
diff changeset
28 @cindex cutting text
Dave Love <fx@gnu.org>
parents:
diff changeset
29 @cindex deletion
59272
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
30 Most commands which erase text from the buffer save it in the kill
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
31 ring. These commands are known as @dfn{kill} commands. The commands
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
32 that erase text but do not save it in the kill ring are known as
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
33 @dfn{delete} commands. The @kbd{C-x u} (@code{undo}) command
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
34 (@pxref{Undo}) can undo both kill and delete commands; the importance
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
35 of the kill ring is that you can also yank the text in a different
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
36 place or places. Emacs has only one kill ring for all buffers, so you
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
37 can kill text in one buffer and yank it in another buffer.
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
38
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
39 The delete commands include @kbd{C-d} (@code{delete-char}) and
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
40 @key{DEL} (@code{delete-backward-char}), which delete only one
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
41 character at a time, and those commands that delete only spaces or
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
42 newlines. Commands that can erase significant amounts of nontrivial
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
43 data generally do a kill operation instead. The commands' names and
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
44 individual descriptions use the words @samp{kill} and @samp{delete} to
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
45 say which kind of operation they perform.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
46
30771
e9948dd313fa (Killing): Document kill-read-only-ok.
Eli Zaretskii <eliz@gnu.org>
parents: 27749
diff changeset
47 @vindex kill-read-only-ok
e9948dd313fa (Killing): Document kill-read-only-ok.
Eli Zaretskii <eliz@gnu.org>
parents: 27749
diff changeset
48 @cindex read-only text, killing
36162
f657bb5a6cf5 Rewrite kill-read-only-ok, Delete Selection mode, replace-rectangle.
Richard M. Stallman <rms@gnu.org>
parents: 35918
diff changeset
49 You cannot kill read-only text, since such text does not allow any
f657bb5a6cf5 Rewrite kill-read-only-ok, Delete Selection mode, replace-rectangle.
Richard M. Stallman <rms@gnu.org>
parents: 35918
diff changeset
50 kind of modification. But some users like to use the kill commands to
f657bb5a6cf5 Rewrite kill-read-only-ok, Delete Selection mode, replace-rectangle.
Richard M. Stallman <rms@gnu.org>
parents: 35918
diff changeset
51 copy read-only text into the kill ring, without actually changing it.
56899
36c1c98acd4b (Killing): Correct description of kill commands in read-only buffer.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56810
diff changeset
52 Therefore, the kill commands work specially in a read-only buffer:
36c1c98acd4b (Killing): Correct description of kill commands in read-only buffer.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56810
diff changeset
53 they move over text, and copy it to the kill ring, without actually
59272
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
54 deleting it from the buffer. Normally, kill commands beep and display
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
55 an error message when this happens. But if you set the variable
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
56 @code{kill-read-only-ok} to a non-@code{nil} value, they just print a
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
57 message in the echo area to explain why the text has not been erased.
30865
fb3d8e6e0497 delete-selection-mode
Dave Love <fx@gnu.org>
parents: 30771
diff changeset
58
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
59 @menu
Dave Love <fx@gnu.org>
parents:
diff changeset
60 * Deletion:: Commands for deleting small amounts of text and
Dave Love <fx@gnu.org>
parents:
diff changeset
61 blank areas.
Dave Love <fx@gnu.org>
parents:
diff changeset
62 * Killing by Lines:: How to kill entire lines of text at one time.
Dave Love <fx@gnu.org>
parents:
diff changeset
63 * Other Kill Commands:: Commands to kill large regions of text and
49600
23a1cea22d13 Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents: 49330
diff changeset
64 syntactic units such as words and sentences.
59272
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
65 * Graphical Kill:: The kill ring on graphical terminals:
2d8dd256436f (Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents: 56899
diff changeset
66 yanking between applications.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
67 @end menu
Dave Love <fx@gnu.org>
parents:
diff changeset
68
37486
d7bf0f33e402 Add @need before Deletion node.
Richard M. Stallman <rms@gnu.org>
parents: 37447
diff changeset
69 @need 1500
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
70 @node Deletion
Dave Love <fx@gnu.org>
parents:
diff changeset
71 @subsection Deletion
Dave Love <fx@gnu.org>
parents:
diff changeset
72 @findex delete-backward-char
Dave Love <fx@gnu.org>
parents:
diff changeset
73 @findex delete-char
Dave Love <fx@gnu.org>
parents:
diff changeset
74
37887
1ebd03c6b468 Add some intro text in node Deletion.
Richard M. Stallman <rms@gnu.org>
parents: 37585
diff changeset
75 Deletion means erasing text and not saving it in the kill ring. For
1ebd03c6b468 Add some intro text in node Deletion.
Richard M. Stallman <rms@gnu.org>
parents: 37585
diff changeset
76 the most part, the Emacs commands that delete text are those that
1ebd03c6b468 Add some intro text in node Deletion.
Richard M. Stallman <rms@gnu.org>
parents: 37585
diff changeset
77 erase just one character or only whitespace.
1ebd03c6b468 Add some intro text in node Deletion.
Richard M. Stallman <rms@gnu.org>
parents: 37585
diff changeset
78
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
79 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
80 @item C-d
36657
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
81 @itemx @key{Delete}
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
82 Delete next character (@code{delete-char}). If your keyboard has a
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
83 @key{Delete} function key (usually located in the edit keypad), Emacs
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
84 binds it to @code{delete-char} as well.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
85 @item @key{DEL}
36657
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
86 @itemx @key{BS}
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
87 Delete previous character (@code{delete-backward-char}). Some keyboards
37486
d7bf0f33e402 Add @need before Deletion node.
Richard M. Stallman <rms@gnu.org>
parents: 37447
diff changeset
88 refer to this key as a ``backspace key'' and label it with a left arrow.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
89 @item M-\
Dave Love <fx@gnu.org>
parents:
diff changeset
90 Delete spaces and tabs around point (@code{delete-horizontal-space}).
Dave Love <fx@gnu.org>
parents:
diff changeset
91 @item M-@key{SPC}
Dave Love <fx@gnu.org>
parents:
diff changeset
92 Delete spaces and tabs around point, leaving one space
Dave Love <fx@gnu.org>
parents:
diff changeset
93 (@code{just-one-space}).
Dave Love <fx@gnu.org>
parents:
diff changeset
94 @item C-x C-o
Dave Love <fx@gnu.org>
parents:
diff changeset
95 Delete blank lines around the current line (@code{delete-blank-lines}).
Dave Love <fx@gnu.org>
parents:
diff changeset
96 @item M-^
Dave Love <fx@gnu.org>
parents:
diff changeset
97 Join two lines by deleting the intervening newline, along with any
Dave Love <fx@gnu.org>
parents:
diff changeset
98 indentation following it (@code{delete-indentation}).
Dave Love <fx@gnu.org>
parents:
diff changeset
99 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
100
36725
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
101 @kindex DEL
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
102 @kindex C-d
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
103 The most basic delete commands are @kbd{C-d} (@code{delete-char}) and
Dave Love <fx@gnu.org>
parents:
diff changeset
104 @key{DEL} (@code{delete-backward-char}). @kbd{C-d} deletes the
Dave Love <fx@gnu.org>
parents:
diff changeset
105 character after point, the one the cursor is ``on top of.'' This
Dave Love <fx@gnu.org>
parents:
diff changeset
106 doesn't move point. @key{DEL} deletes the character before the cursor,
Dave Love <fx@gnu.org>
parents:
diff changeset
107 and moves point back. You can delete newlines like any other characters
Dave Love <fx@gnu.org>
parents:
diff changeset
108 in the buffer; deleting a newline joins two lines. Actually, @kbd{C-d}
Dave Love <fx@gnu.org>
parents:
diff changeset
109 and @key{DEL} aren't always delete commands; when given arguments, they
Dave Love <fx@gnu.org>
parents:
diff changeset
110 kill instead, since they can erase more than one character this way.
Dave Love <fx@gnu.org>
parents:
diff changeset
111
36725
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
112 @kindex BACKSPACE
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
113 @kindex BS
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
114 @kindex DELETE
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
115 Every keyboard has a large key, labeled @key{DEL}, @key{BACKSPACE},
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
116 @key{BS} or @key{DELETE}, which is a short distance above the
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
117 @key{RET} or @key{ENTER} key and is normally used for erasing what you
36789
f71fe44b07ea Simplify the discussion of DEL. Refer to `DEL Gets Help' node
Richard M. Stallman <rms@gnu.org>
parents: 36725
diff changeset
118 have typed. Regardless of the actual name on the key, in Emacs it is
36725
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
119 equivalent to @key{DEL}---or it should be.
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
120
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
121 Many keyboards (including standard PC keyboards) have a
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
122 @key{BACKSPACE} key a short ways above @key{RET} or @key{ENTER}, and a
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
123 @key{DELETE} key elsewhere. In that case, the @key{BACKSPACE} key is
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
124 @key{DEL}, and the @key{DELETE} key is equivalent to @kbd{C-d}---or it
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
125 should be.
36725
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
126
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
127 Why do we say ``or it should be''? When Emacs starts up using a
36789
f71fe44b07ea Simplify the discussion of DEL. Refer to `DEL Gets Help' node
Richard M. Stallman <rms@gnu.org>
parents: 36725
diff changeset
128 window system, it determines automatically which key or keys should be
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
129 equivalent to @key{DEL}. As a result, @key{BACKSPACE} and/or @key{DELETE}
36789
f71fe44b07ea Simplify the discussion of DEL. Refer to `DEL Gets Help' node
Richard M. Stallman <rms@gnu.org>
parents: 36725
diff changeset
130 keys normally do the right things. But in some unusual cases Emacs
f71fe44b07ea Simplify the discussion of DEL. Refer to `DEL Gets Help' node
Richard M. Stallman <rms@gnu.org>
parents: 36725
diff changeset
131 gets the wrong information from the system. If these keys don't do
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
132 what they ought to do, you need to tell Emacs which key to use for
38767
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38745
diff changeset
133 @key{DEL}. @xref{DEL Does Not Delete}, for how to do this.
36725
640fb21a2098 Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents: 36720
diff changeset
134
36789
f71fe44b07ea Simplify the discussion of DEL. Refer to `DEL Gets Help' node
Richard M. Stallman <rms@gnu.org>
parents: 36725
diff changeset
135 @findex normal-erase-is-backspace-mode
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
136 On most text-only terminals, Emacs cannot tell which keys the
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
137 keyboard really has, so it follows a uniform plan which may or may not
52979
3649390c0f91 Replace @sc{ascii} and ASCII with @acronym{ASCII}.
Eli Zaretskii <eliz@gnu.org>
parents: 52401
diff changeset
138 fit your keyboard. The uniform plan is that the @acronym{ASCII} @key{DEL}
3649390c0f91 Replace @sc{ascii} and ASCII with @acronym{ASCII}.
Eli Zaretskii <eliz@gnu.org>
parents: 52401
diff changeset
139 character deletes, and the @acronym{ASCII} @key{BS} (backspace) character asks
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37124
diff changeset
140 for help (it is the same as @kbd{C-h}). If this is not right for your
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
141 keyboard, such as if you find that the key which ought to delete backwards
38767
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38745
diff changeset
142 enters Help instead, see @ref{DEL Does Not Delete}.
36657
0ee33338bb24 (Deletion): Mention the Delete vs Backspace keys. Document
Eli Zaretskii <eliz@gnu.org>
parents: 36162
diff changeset
143
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
144 @kindex M-\
Dave Love <fx@gnu.org>
parents:
diff changeset
145 @findex delete-horizontal-space
Dave Love <fx@gnu.org>
parents:
diff changeset
146 @kindex M-SPC
Dave Love <fx@gnu.org>
parents:
diff changeset
147 @findex just-one-space
Dave Love <fx@gnu.org>
parents:
diff changeset
148 The other delete commands are those which delete only whitespace
Dave Love <fx@gnu.org>
parents:
diff changeset
149 characters: spaces, tabs and newlines. @kbd{M-\}
Dave Love <fx@gnu.org>
parents:
diff changeset
150 (@code{delete-horizontal-space}) deletes all the spaces and tab
Dave Love <fx@gnu.org>
parents:
diff changeset
151 characters before and after point. @kbd{M-@key{SPC}}
Dave Love <fx@gnu.org>
parents:
diff changeset
152 (@code{just-one-space}) does likewise but leaves a single space after
Dave Love <fx@gnu.org>
parents:
diff changeset
153 point, regardless of the number of spaces that existed previously (even
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
154 if there were none before).
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
155
Dave Love <fx@gnu.org>
parents:
diff changeset
156 @kbd{C-x C-o} (@code{delete-blank-lines}) deletes all blank lines
Dave Love <fx@gnu.org>
parents:
diff changeset
157 after the current line. If the current line is blank, it deletes all
Dave Love <fx@gnu.org>
parents:
diff changeset
158 blank lines preceding the current line as well (leaving one blank line,
Dave Love <fx@gnu.org>
parents:
diff changeset
159 the current line).
Dave Love <fx@gnu.org>
parents:
diff changeset
160
Dave Love <fx@gnu.org>
parents:
diff changeset
161 @kbd{M-^} (@code{delete-indentation}) joins the current line and the
Dave Love <fx@gnu.org>
parents:
diff changeset
162 previous line, by deleting a newline and all surrounding spaces, usually
Dave Love <fx@gnu.org>
parents:
diff changeset
163 leaving a single space. @xref{Indentation,M-^}.
Dave Love <fx@gnu.org>
parents:
diff changeset
164
Dave Love <fx@gnu.org>
parents:
diff changeset
165 @node Killing by Lines
Dave Love <fx@gnu.org>
parents:
diff changeset
166 @subsection Killing by Lines
Dave Love <fx@gnu.org>
parents:
diff changeset
167
Dave Love <fx@gnu.org>
parents:
diff changeset
168 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
169 @item C-k
Dave Love <fx@gnu.org>
parents:
diff changeset
170 Kill rest of line or one or more lines (@code{kill-line}).
Dave Love <fx@gnu.org>
parents:
diff changeset
171 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
172
Dave Love <fx@gnu.org>
parents:
diff changeset
173 @kindex C-k
Dave Love <fx@gnu.org>
parents:
diff changeset
174 @findex kill-line
Dave Love <fx@gnu.org>
parents:
diff changeset
175 The simplest kill command is @kbd{C-k}. If given at the beginning of
Dave Love <fx@gnu.org>
parents:
diff changeset
176 a line, it kills all the text on the line, leaving it blank. When used
Dave Love <fx@gnu.org>
parents:
diff changeset
177 on a blank line, it kills the whole line including its newline. To kill
Dave Love <fx@gnu.org>
parents:
diff changeset
178 an entire non-blank line, go to the beginning and type @kbd{C-k} twice.
Dave Love <fx@gnu.org>
parents:
diff changeset
179
Dave Love <fx@gnu.org>
parents:
diff changeset
180 More generally, @kbd{C-k} kills from point up to the end of the line,
Dave Love <fx@gnu.org>
parents:
diff changeset
181 unless it is at the end of a line. In that case it kills the newline
Dave Love <fx@gnu.org>
parents:
diff changeset
182 following point, thus merging the next line into the current one.
Dave Love <fx@gnu.org>
parents:
diff changeset
183 Spaces and tabs that you can't see at the end of the line are ignored
Dave Love <fx@gnu.org>
parents:
diff changeset
184 when deciding which case applies, so if point appears to be at the end
Dave Love <fx@gnu.org>
parents:
diff changeset
185 of the line, you can be sure @kbd{C-k} will kill the newline.
Dave Love <fx@gnu.org>
parents:
diff changeset
186
Dave Love <fx@gnu.org>
parents:
diff changeset
187 When @kbd{C-k} is given a positive argument, it kills that many lines
Dave Love <fx@gnu.org>
parents:
diff changeset
188 and the newlines that follow them (however, text on the current line
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
189 before point is not killed). With a negative argument @minus{}@var{n}, it
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
190 kills @var{n} lines preceding the current line (together with the text
Dave Love <fx@gnu.org>
parents:
diff changeset
191 on the current line before point). Thus, @kbd{C-u - 2 C-k} at the front
Dave Love <fx@gnu.org>
parents:
diff changeset
192 of a line kills the two previous lines.
Dave Love <fx@gnu.org>
parents:
diff changeset
193
Dave Love <fx@gnu.org>
parents:
diff changeset
194 @kbd{C-k} with an argument of zero kills the text before point on the
Dave Love <fx@gnu.org>
parents:
diff changeset
195 current line.
Dave Love <fx@gnu.org>
parents:
diff changeset
196
Dave Love <fx@gnu.org>
parents:
diff changeset
197 @vindex kill-whole-line
Dave Love <fx@gnu.org>
parents:
diff changeset
198 If the variable @code{kill-whole-line} is non-@code{nil}, @kbd{C-k} at
Dave Love <fx@gnu.org>
parents:
diff changeset
199 the very beginning of a line kills the entire line including the
Dave Love <fx@gnu.org>
parents:
diff changeset
200 following newline. This variable is normally @code{nil}.
Dave Love <fx@gnu.org>
parents:
diff changeset
201
Dave Love <fx@gnu.org>
parents:
diff changeset
202 @node Other Kill Commands
Dave Love <fx@gnu.org>
parents:
diff changeset
203 @subsection Other Kill Commands
Dave Love <fx@gnu.org>
parents:
diff changeset
204 @findex kill-region
Dave Love <fx@gnu.org>
parents:
diff changeset
205 @kindex C-w
Dave Love <fx@gnu.org>
parents:
diff changeset
206
Dave Love <fx@gnu.org>
parents:
diff changeset
207 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
208 @item C-w
Dave Love <fx@gnu.org>
parents:
diff changeset
209 Kill region (from point to the mark) (@code{kill-region}).
Dave Love <fx@gnu.org>
parents:
diff changeset
210 @item M-d
Dave Love <fx@gnu.org>
parents:
diff changeset
211 Kill word (@code{kill-word}). @xref{Words}.
Dave Love <fx@gnu.org>
parents:
diff changeset
212 @item M-@key{DEL}
Dave Love <fx@gnu.org>
parents:
diff changeset
213 Kill word backwards (@code{backward-kill-word}).
Dave Love <fx@gnu.org>
parents:
diff changeset
214 @item C-x @key{DEL}
Dave Love <fx@gnu.org>
parents:
diff changeset
215 Kill back to beginning of sentence (@code{backward-kill-sentence}).
Dave Love <fx@gnu.org>
parents:
diff changeset
216 @xref{Sentences}.
Dave Love <fx@gnu.org>
parents:
diff changeset
217 @item M-k
Dave Love <fx@gnu.org>
parents:
diff changeset
218 Kill to end of sentence (@code{kill-sentence}).
Dave Love <fx@gnu.org>
parents:
diff changeset
219 @item C-M-k
38206
b13ab91e3dd8 Say "expression" instead of "sexp". Update xref, Sexps -> Expressions.
Richard M. Stallman <rms@gnu.org>
parents: 37887
diff changeset
220 Kill the following balanced expression (@code{kill-sexp}). @xref{Expressions}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
221 @item M-z @var{char}
Dave Love <fx@gnu.org>
parents:
diff changeset
222 Kill through the next occurrence of @var{char} (@code{zap-to-char}).
Dave Love <fx@gnu.org>
parents:
diff changeset
223 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
224
59951
c2c2b868b75f (Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents: 59284
diff changeset
225 The most general kill command is @kbd{C-w} (@code{kill-region}),
c2c2b868b75f (Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents: 59284
diff changeset
226 which kills everything between point and the mark. With this command,
c2c2b868b75f (Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents: 59284
diff changeset
227 you can kill any contiguous sequence of characters, if you first set
c2c2b868b75f (Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents: 59284
diff changeset
228 the region around them.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
229
Dave Love <fx@gnu.org>
parents:
diff changeset
230 @kindex M-z
Dave Love <fx@gnu.org>
parents:
diff changeset
231 @findex zap-to-char
Dave Love <fx@gnu.org>
parents:
diff changeset
232 A convenient way of killing is combined with searching: @kbd{M-z}
Dave Love <fx@gnu.org>
parents:
diff changeset
233 (@code{zap-to-char}) reads a character and kills from point up to (and
Dave Love <fx@gnu.org>
parents:
diff changeset
234 including) the next occurrence of that character in the buffer. A
Dave Love <fx@gnu.org>
parents:
diff changeset
235 numeric argument acts as a repeat count. A negative argument means to
Dave Love <fx@gnu.org>
parents:
diff changeset
236 search backward and kill text before point.
Dave Love <fx@gnu.org>
parents:
diff changeset
237
38206
b13ab91e3dd8 Say "expression" instead of "sexp". Update xref, Sexps -> Expressions.
Richard M. Stallman <rms@gnu.org>
parents: 37887
diff changeset
238 Other syntactic units can be killed: words, with @kbd{M-@key{DEL}}
b13ab91e3dd8 Say "expression" instead of "sexp". Update xref, Sexps -> Expressions.
Richard M. Stallman <rms@gnu.org>
parents: 37887
diff changeset
239 and @kbd{M-d} (@pxref{Words}); balanced expressions, with @kbd{C-M-k}
b13ab91e3dd8 Say "expression" instead of "sexp". Update xref, Sexps -> Expressions.
Richard M. Stallman <rms@gnu.org>
parents: 37887
diff changeset
240 (@pxref{Expressions}); and sentences, with @kbd{C-x @key{DEL}} and
b13ab91e3dd8 Say "expression" instead of "sexp". Update xref, Sexps -> Expressions.
Richard M. Stallman <rms@gnu.org>
parents: 37887
diff changeset
241 @kbd{M-k} (@pxref{Sentences}).@refill
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
242
59284
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
243 @node Graphical Kill
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
244 @subsection Killing on Graphical Terminals
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
245
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
246 On multi-window terminals, the most recent kill done in Emacs is
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
247 also the primary selection, if it is more recent than any selection
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
248 you made in another program. This means that the paste commands of
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
249 other applications with separate windows copy the text that you killed
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
250 in Emacs. In addition, Emacs yank commands treat other applications'
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
251 selections as part of the kill ring, so you can yank them into Emacs.
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
252
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
253 @cindex Delete Selection mode
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
254 @cindex mode, Delete Selection
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
255 @findex delete-selection-mode
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
256 Many window systems follow the convention that insertion while text
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
257 is selected deletes the selected text. You can make Emacs behave this
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
258 way by enabling Delete Selection mode, with @kbd{M-x
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
259 delete-selection-mode}, or using Custom. Another effect of this mode
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
260 is that @key{DEL}, @kbd{C-d} and some other keys, when a selection
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
261 exists, will kill the whole selection. It also enables Transient Mark
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
262 mode (@pxref{Transient Mark}).
54ff1fbcac20 (Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents: 59272
diff changeset
263
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
264 @node Yanking, Accumulating Text, Killing, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
265 @section Yanking
Dave Love <fx@gnu.org>
parents:
diff changeset
266 @cindex moving text
Dave Love <fx@gnu.org>
parents:
diff changeset
267 @cindex copying text
Dave Love <fx@gnu.org>
parents:
diff changeset
268 @cindex kill ring
Dave Love <fx@gnu.org>
parents:
diff changeset
269 @cindex yanking
Dave Love <fx@gnu.org>
parents:
diff changeset
270 @cindex pasting
Dave Love <fx@gnu.org>
parents:
diff changeset
271
Dave Love <fx@gnu.org>
parents:
diff changeset
272 @dfn{Yanking} means reinserting text previously killed. This is what
Dave Love <fx@gnu.org>
parents:
diff changeset
273 some systems call ``pasting.'' The usual way to move or copy text is to
56692
ccb70b8731b4 (Yanking, Killing): Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 52979
diff changeset
274 kill it and then yank it elsewhere one or more times. This is very safe
ccb70b8731b4 (Yanking, Killing): Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 52979
diff changeset
275 because Emacs remembers many recent kills, not just the last one.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
276
Dave Love <fx@gnu.org>
parents:
diff changeset
277 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
278 @item C-y
Dave Love <fx@gnu.org>
parents:
diff changeset
279 Yank last killed text (@code{yank}).
Dave Love <fx@gnu.org>
parents:
diff changeset
280 @item M-y
Dave Love <fx@gnu.org>
parents:
diff changeset
281 Replace text just yanked with an earlier batch of killed text
Dave Love <fx@gnu.org>
parents:
diff changeset
282 (@code{yank-pop}).
Dave Love <fx@gnu.org>
parents:
diff changeset
283 @item M-w
Dave Love <fx@gnu.org>
parents:
diff changeset
284 Save region as last killed text without actually killing it
59951
c2c2b868b75f (Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents: 59284
diff changeset
285 (@code{kill-ring-save}). Some systems call this ``copying''.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
286 @item C-M-w
Dave Love <fx@gnu.org>
parents:
diff changeset
287 Append next kill to last batch of killed text (@code{append-next-kill}).
Dave Love <fx@gnu.org>
parents:
diff changeset
288 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
289
46037
7af49c69e77b Mention that kill commands communicate with other apps,
Richard M. Stallman <rms@gnu.org>
parents: 39264
diff changeset
290 On window systems, if there is a current selection in some other
7af49c69e77b Mention that kill commands communicate with other apps,
Richard M. Stallman <rms@gnu.org>
parents: 39264
diff changeset
291 application, and you selected it more recently than you killed any
7af49c69e77b Mention that kill commands communicate with other apps,
Richard M. Stallman <rms@gnu.org>
parents: 39264
diff changeset
292 text in Emacs, @kbd{C-y} copies the selection instead of text
7af49c69e77b Mention that kill commands communicate with other apps,
Richard M. Stallman <rms@gnu.org>
parents: 39264
diff changeset
293 killed within Emacs.
7af49c69e77b Mention that kill commands communicate with other apps,
Richard M. Stallman <rms@gnu.org>
parents: 39264
diff changeset
294
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
295 @menu
Dave Love <fx@gnu.org>
parents:
diff changeset
296 * Kill Ring:: Where killed text is stored. Basic yanking.
Dave Love <fx@gnu.org>
parents:
diff changeset
297 * Appending Kills:: Several kills in a row all yank together.
Dave Love <fx@gnu.org>
parents:
diff changeset
298 * Earlier Kills:: Yanking something killed some time ago.
Dave Love <fx@gnu.org>
parents:
diff changeset
299 @end menu
Dave Love <fx@gnu.org>
parents:
diff changeset
300
Dave Love <fx@gnu.org>
parents:
diff changeset
301 @node Kill Ring
Dave Love <fx@gnu.org>
parents:
diff changeset
302 @subsection The Kill Ring
Dave Love <fx@gnu.org>
parents:
diff changeset
303
Dave Love <fx@gnu.org>
parents:
diff changeset
304 All killed text is recorded in the @dfn{kill ring}, a list of blocks of
Dave Love <fx@gnu.org>
parents:
diff changeset
305 text that have been killed. There is only one kill ring, shared by all
Dave Love <fx@gnu.org>
parents:
diff changeset
306 buffers, so you can kill text in one buffer and yank it in another buffer.
Dave Love <fx@gnu.org>
parents:
diff changeset
307 This is the usual way to move text from one file to another.
Dave Love <fx@gnu.org>
parents:
diff changeset
308 (@xref{Accumulating Text}, for some other ways.)
Dave Love <fx@gnu.org>
parents:
diff changeset
309
Dave Love <fx@gnu.org>
parents:
diff changeset
310 @kindex C-y
Dave Love <fx@gnu.org>
parents:
diff changeset
311 @findex yank
Dave Love <fx@gnu.org>
parents:
diff changeset
312 The command @kbd{C-y} (@code{yank}) reinserts the text of the most recent
Dave Love <fx@gnu.org>
parents:
diff changeset
313 kill. It leaves the cursor at the end of the text. It sets the mark at
Dave Love <fx@gnu.org>
parents:
diff changeset
314 the beginning of the text. @xref{Mark}.
Dave Love <fx@gnu.org>
parents:
diff changeset
315
Dave Love <fx@gnu.org>
parents:
diff changeset
316 @kbd{C-u C-y} leaves the cursor in front of the text, and sets the
Dave Love <fx@gnu.org>
parents:
diff changeset
317 mark after it. This happens only if the argument is specified with just
Dave Love <fx@gnu.org>
parents:
diff changeset
318 a @kbd{C-u}, precisely. Any other sort of argument, including @kbd{C-u}
Dave Love <fx@gnu.org>
parents:
diff changeset
319 and digits, specifies an earlier kill to yank (@pxref{Earlier Kills}).
Dave Love <fx@gnu.org>
parents:
diff changeset
320
46241
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
321 @cindex yanking and text properties
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
322 @vindex yank-excluded-properties
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
323 The yank commands discard certain text properties from the text that
47200
617a371d38f2 Fix typo.
Richard M. Stallman <rms@gnu.org>
parents: 46241
diff changeset
324 is yanked, those that might lead to annoying results. For instance,
46241
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
325 they discard text properties that respond to the mouse or specify key
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
326 bindings. The variable @code{yank-excluded-properties} specifies the
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
327 properties to discard. Yanking of register contents and rectangles
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
328 also discard these properties.
0ed85ef15043 Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents: 46037
diff changeset
329
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
330 @kindex M-w
Dave Love <fx@gnu.org>
parents:
diff changeset
331 @findex kill-ring-save
Dave Love <fx@gnu.org>
parents:
diff changeset
332 To copy a block of text, you can use @kbd{M-w}
Dave Love <fx@gnu.org>
parents:
diff changeset
333 (@code{kill-ring-save}), which copies the region into the kill ring
Dave Love <fx@gnu.org>
parents:
diff changeset
334 without removing it from the buffer. This is approximately equivalent
Dave Love <fx@gnu.org>
parents:
diff changeset
335 to @kbd{C-w} followed by @kbd{C-x u}, except that @kbd{M-w} does not
Dave Love <fx@gnu.org>
parents:
diff changeset
336 alter the undo history and does not temporarily change the screen.
Dave Love <fx@gnu.org>
parents:
diff changeset
337
Dave Love <fx@gnu.org>
parents:
diff changeset
338 @node Appending Kills
Dave Love <fx@gnu.org>
parents:
diff changeset
339 @subsection Appending Kills
Dave Love <fx@gnu.org>
parents:
diff changeset
340
Dave Love <fx@gnu.org>
parents:
diff changeset
341 @cindex appending kills in the ring
Dave Love <fx@gnu.org>
parents:
diff changeset
342 @cindex television
Dave Love <fx@gnu.org>
parents:
diff changeset
343 Normally, each kill command pushes a new entry onto the kill ring.
Dave Love <fx@gnu.org>
parents:
diff changeset
344 However, two or more kill commands in a row combine their text into a
Dave Love <fx@gnu.org>
parents:
diff changeset
345 single entry, so that a single @kbd{C-y} yanks all the text as a unit,
Dave Love <fx@gnu.org>
parents:
diff changeset
346 just as it was before it was killed.
Dave Love <fx@gnu.org>
parents:
diff changeset
347
Dave Love <fx@gnu.org>
parents:
diff changeset
348 Thus, if you want to yank text as a unit, you need not kill all of it
Dave Love <fx@gnu.org>
parents:
diff changeset
349 with one command; you can keep killing line after line, or word after
Dave Love <fx@gnu.org>
parents:
diff changeset
350 word, until you have killed it all, and you can still get it all back at
Dave Love <fx@gnu.org>
parents:
diff changeset
351 once.
Dave Love <fx@gnu.org>
parents:
diff changeset
352
Dave Love <fx@gnu.org>
parents:
diff changeset
353 Commands that kill forward from point add onto the end of the previous
Dave Love <fx@gnu.org>
parents:
diff changeset
354 killed text. Commands that kill backward from point add text onto the
Dave Love <fx@gnu.org>
parents:
diff changeset
355 beginning. This way, any sequence of mixed forward and backward kill
Dave Love <fx@gnu.org>
parents:
diff changeset
356 commands puts all the killed text into one entry without rearrangement.
Dave Love <fx@gnu.org>
parents:
diff changeset
357 Numeric arguments do not break the sequence of appending kills. For
Dave Love <fx@gnu.org>
parents:
diff changeset
358 example, suppose the buffer contains this text:
Dave Love <fx@gnu.org>
parents:
diff changeset
359
Dave Love <fx@gnu.org>
parents:
diff changeset
360 @example
Dave Love <fx@gnu.org>
parents:
diff changeset
361 This is a line @point{}of sample text.
Dave Love <fx@gnu.org>
parents:
diff changeset
362 @end example
Dave Love <fx@gnu.org>
parents:
diff changeset
363
Dave Love <fx@gnu.org>
parents:
diff changeset
364 @noindent
Dave Love <fx@gnu.org>
parents:
diff changeset
365 with point shown by @point{}. If you type @kbd{M-d M-@key{DEL} M-d
Dave Love <fx@gnu.org>
parents:
diff changeset
366 M-@key{DEL}}, killing alternately forward and backward, you end up with
Dave Love <fx@gnu.org>
parents:
diff changeset
367 @samp{a line of sample} as one entry in the kill ring, and @samp{This
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
368 is@ @ text.} in the buffer. (Note the double space between @samp{is}
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
369 and @samp{text}, which you can clean up with @kbd{M-@key{SPC}} or
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
370 @kbd{M-q}.)
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
371
Dave Love <fx@gnu.org>
parents:
diff changeset
372 Another way to kill the same text is to move back two words with
Dave Love <fx@gnu.org>
parents:
diff changeset
373 @kbd{M-b M-b}, then kill all four words forward with @kbd{C-u M-d}.
Dave Love <fx@gnu.org>
parents:
diff changeset
374 This produces exactly the same results in the buffer and in the kill
Dave Love <fx@gnu.org>
parents:
diff changeset
375 ring. @kbd{M-f M-f C-u M-@key{DEL}} kills the same text, all going
Dave Love <fx@gnu.org>
parents:
diff changeset
376 backward; once again, the result is the same. The text in the kill ring
Dave Love <fx@gnu.org>
parents:
diff changeset
377 entry always has the same order that it had in the buffer before you
Dave Love <fx@gnu.org>
parents:
diff changeset
378 killed it.
Dave Love <fx@gnu.org>
parents:
diff changeset
379
Dave Love <fx@gnu.org>
parents:
diff changeset
380 @kindex C-M-w
Dave Love <fx@gnu.org>
parents:
diff changeset
381 @findex append-next-kill
Dave Love <fx@gnu.org>
parents:
diff changeset
382 If a kill command is separated from the last kill command by other
Dave Love <fx@gnu.org>
parents:
diff changeset
383 commands (not just numeric arguments), it starts a new entry on the kill
Dave Love <fx@gnu.org>
parents:
diff changeset
384 ring. But you can force it to append by first typing the command
Dave Love <fx@gnu.org>
parents:
diff changeset
385 @kbd{C-M-w} (@code{append-next-kill}) right before it. The @kbd{C-M-w}
Dave Love <fx@gnu.org>
parents:
diff changeset
386 tells the following command, if it is a kill command, to append the text
Dave Love <fx@gnu.org>
parents:
diff changeset
387 it kills to the last killed text, instead of starting a new entry. With
Dave Love <fx@gnu.org>
parents:
diff changeset
388 @kbd{C-M-w}, you can kill several separated pieces of text and
Dave Love <fx@gnu.org>
parents:
diff changeset
389 accumulate them to be yanked back in one place.@refill
Dave Love <fx@gnu.org>
parents:
diff changeset
390
Dave Love <fx@gnu.org>
parents:
diff changeset
391 A kill command following @kbd{M-w} does not append to the text that
Dave Love <fx@gnu.org>
parents:
diff changeset
392 @kbd{M-w} copied into the kill ring.
Dave Love <fx@gnu.org>
parents:
diff changeset
393
Dave Love <fx@gnu.org>
parents:
diff changeset
394 @node Earlier Kills
Dave Love <fx@gnu.org>
parents:
diff changeset
395 @subsection Yanking Earlier Kills
Dave Love <fx@gnu.org>
parents:
diff changeset
396
Dave Love <fx@gnu.org>
parents:
diff changeset
397 @cindex yanking previous kills
Dave Love <fx@gnu.org>
parents:
diff changeset
398 @kindex M-y
Dave Love <fx@gnu.org>
parents:
diff changeset
399 @findex yank-pop
Dave Love <fx@gnu.org>
parents:
diff changeset
400 To recover killed text that is no longer the most recent kill, use the
Dave Love <fx@gnu.org>
parents:
diff changeset
401 @kbd{M-y} command (@code{yank-pop}). It takes the text previously
Dave Love <fx@gnu.org>
parents:
diff changeset
402 yanked and replaces it with the text from an earlier kill. So, to
Dave Love <fx@gnu.org>
parents:
diff changeset
403 recover the text of the next-to-the-last kill, first use @kbd{C-y} to
Dave Love <fx@gnu.org>
parents:
diff changeset
404 yank the last kill, and then use @kbd{M-y} to replace it with the
Dave Love <fx@gnu.org>
parents:
diff changeset
405 previous kill. @kbd{M-y} is allowed only after a @kbd{C-y} or another
Dave Love <fx@gnu.org>
parents:
diff changeset
406 @kbd{M-y}.
Dave Love <fx@gnu.org>
parents:
diff changeset
407
Dave Love <fx@gnu.org>
parents:
diff changeset
408 You can understand @kbd{M-y} in terms of a ``last yank'' pointer which
Dave Love <fx@gnu.org>
parents:
diff changeset
409 points at an entry in the kill ring. Each time you kill, the ``last
Dave Love <fx@gnu.org>
parents:
diff changeset
410 yank'' pointer moves to the newly made entry at the front of the ring.
Dave Love <fx@gnu.org>
parents:
diff changeset
411 @kbd{C-y} yanks the entry which the ``last yank'' pointer points to.
Dave Love <fx@gnu.org>
parents:
diff changeset
412 @kbd{M-y} moves the ``last yank'' pointer to a different entry, and the
Dave Love <fx@gnu.org>
parents:
diff changeset
413 text in the buffer changes to match. Enough @kbd{M-y} commands can move
Dave Love <fx@gnu.org>
parents:
diff changeset
414 the pointer to any entry in the ring, so you can get any entry into the
Dave Love <fx@gnu.org>
parents:
diff changeset
415 buffer. Eventually the pointer reaches the end of the ring; the next
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
416 @kbd{M-y} loops back around to the first entry again.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
417
Dave Love <fx@gnu.org>
parents:
diff changeset
418 @kbd{M-y} moves the ``last yank'' pointer around the ring, but it does
Dave Love <fx@gnu.org>
parents:
diff changeset
419 not change the order of the entries in the ring, which always runs from
Dave Love <fx@gnu.org>
parents:
diff changeset
420 the most recent kill at the front to the oldest one still remembered.
Dave Love <fx@gnu.org>
parents:
diff changeset
421
Dave Love <fx@gnu.org>
parents:
diff changeset
422 @kbd{M-y} can take a numeric argument, which tells it how many entries
Dave Love <fx@gnu.org>
parents:
diff changeset
423 to advance the ``last yank'' pointer by. A negative argument moves the
Dave Love <fx@gnu.org>
parents:
diff changeset
424 pointer toward the front of the ring; from the front of the ring, it
Dave Love <fx@gnu.org>
parents:
diff changeset
425 moves ``around'' to the last entry and continues forward from there.
Dave Love <fx@gnu.org>
parents:
diff changeset
426
Dave Love <fx@gnu.org>
parents:
diff changeset
427 Once the text you are looking for is brought into the buffer, you can
Dave Love <fx@gnu.org>
parents:
diff changeset
428 stop doing @kbd{M-y} commands and it will stay there. It's just a copy
Dave Love <fx@gnu.org>
parents:
diff changeset
429 of the kill ring entry, so editing it in the buffer does not change
Dave Love <fx@gnu.org>
parents:
diff changeset
430 what's in the ring. As long as no new killing is done, the ``last
Dave Love <fx@gnu.org>
parents:
diff changeset
431 yank'' pointer remains at the same place in the kill ring, so repeating
Dave Love <fx@gnu.org>
parents:
diff changeset
432 @kbd{C-y} will yank another copy of the same previous kill.
Dave Love <fx@gnu.org>
parents:
diff changeset
433
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
434 If you know how many @kbd{M-y} commands it would take to find the
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
435 text you want, you can yank that text in one step using @kbd{C-y} with
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
436 a numeric argument. @kbd{C-y} with an argument restores the text from
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
437 the specified kill ring entry, counting back from the most recent as
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
438 1. Thus, @kbd{C-u 2 C-y} gets the next-to-the-last block of killed
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
439 text---it is equivalent to @kbd{C-y M-y}. @kbd{C-y} with a numeric
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
440 argument starts counting from the ``last yank'' pointer, and sets the
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
441 ``last yank'' pointer to the entry that it yanks.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
442
Dave Love <fx@gnu.org>
parents:
diff changeset
443 @vindex kill-ring-max
Dave Love <fx@gnu.org>
parents:
diff changeset
444 The length of the kill ring is controlled by the variable
Dave Love <fx@gnu.org>
parents:
diff changeset
445 @code{kill-ring-max}; no more than that many blocks of killed text are
Dave Love <fx@gnu.org>
parents:
diff changeset
446 saved.
Dave Love <fx@gnu.org>
parents:
diff changeset
447
Dave Love <fx@gnu.org>
parents:
diff changeset
448 @vindex kill-ring
Dave Love <fx@gnu.org>
parents:
diff changeset
449 The actual contents of the kill ring are stored in a variable named
Dave Love <fx@gnu.org>
parents:
diff changeset
450 @code{kill-ring}; you can view the entire contents of the kill ring with
Dave Love <fx@gnu.org>
parents:
diff changeset
451 the command @kbd{C-h v kill-ring}.
Dave Love <fx@gnu.org>
parents:
diff changeset
452
Dave Love <fx@gnu.org>
parents:
diff changeset
453 @node Accumulating Text, Rectangles, Yanking, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
454 @section Accumulating Text
Dave Love <fx@gnu.org>
parents:
diff changeset
455 @findex append-to-buffer
Dave Love <fx@gnu.org>
parents:
diff changeset
456 @findex prepend-to-buffer
Dave Love <fx@gnu.org>
parents:
diff changeset
457 @findex copy-to-buffer
Dave Love <fx@gnu.org>
parents:
diff changeset
458 @findex append-to-file
Dave Love <fx@gnu.org>
parents:
diff changeset
459
Dave Love <fx@gnu.org>
parents:
diff changeset
460 @cindex accumulating scattered text
Dave Love <fx@gnu.org>
parents:
diff changeset
461 Usually we copy or move text by killing it and yanking it, but there
59951
c2c2b868b75f (Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents: 59284
diff changeset
462 are other convenient methods for copying one block of text in many
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
463 places, or for copying many scattered blocks of text into one place. To
Dave Love <fx@gnu.org>
parents:
diff changeset
464 copy one block to many places, store it in a register
Dave Love <fx@gnu.org>
parents:
diff changeset
465 (@pxref{Registers}). Here we describe the commands to accumulate
Dave Love <fx@gnu.org>
parents:
diff changeset
466 scattered pieces of text into a buffer or into a file.
Dave Love <fx@gnu.org>
parents:
diff changeset
467
Dave Love <fx@gnu.org>
parents:
diff changeset
468 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
469 @item M-x append-to-buffer
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
470 Append region to the contents of a specified buffer.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
471 @item M-x prepend-to-buffer
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
472 Prepend region to the contents of a specified buffer.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
473 @item M-x copy-to-buffer
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
474 Copy region into a specified buffer, deleting that buffer's old contents.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
475 @item M-x insert-buffer
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
476 Insert the contents of a specified buffer into current buffer at point.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
477 @item M-x append-to-file
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
478 Append region to the contents of a specified file, at the end.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
479 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
480
Dave Love <fx@gnu.org>
parents:
diff changeset
481 To accumulate text into a buffer, use @kbd{M-x append-to-buffer}.
Dave Love <fx@gnu.org>
parents:
diff changeset
482 This reads a buffer name, then inserts a copy of the region into the
Dave Love <fx@gnu.org>
parents:
diff changeset
483 buffer specified. If you specify a nonexistent buffer,
Dave Love <fx@gnu.org>
parents:
diff changeset
484 @code{append-to-buffer} creates the buffer. The text is inserted
Dave Love <fx@gnu.org>
parents:
diff changeset
485 wherever point is in that buffer. If you have been using the buffer for
Dave Love <fx@gnu.org>
parents:
diff changeset
486 editing, the copied text goes into the middle of the text of the buffer,
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
487 starting from wherever point happens to be at that moment.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
488
Dave Love <fx@gnu.org>
parents:
diff changeset
489 Point in that buffer is left at the end of the copied text, so
Dave Love <fx@gnu.org>
parents:
diff changeset
490 successive uses of @code{append-to-buffer} accumulate the text in the
Dave Love <fx@gnu.org>
parents:
diff changeset
491 specified buffer in the same order as they were copied. Strictly
Dave Love <fx@gnu.org>
parents:
diff changeset
492 speaking, @code{append-to-buffer} does not always append to the text
Dave Love <fx@gnu.org>
parents:
diff changeset
493 already in the buffer---it appends only if point in that buffer is at the end.
Dave Love <fx@gnu.org>
parents:
diff changeset
494 However, if @code{append-to-buffer} is the only command you use to alter
Dave Love <fx@gnu.org>
parents:
diff changeset
495 a buffer, then point is always at the end.
Dave Love <fx@gnu.org>
parents:
diff changeset
496
Dave Love <fx@gnu.org>
parents:
diff changeset
497 @kbd{M-x prepend-to-buffer} is just like @code{append-to-buffer}
Dave Love <fx@gnu.org>
parents:
diff changeset
498 except that point in the other buffer is left before the copied text, so
Dave Love <fx@gnu.org>
parents:
diff changeset
499 successive prependings add text in reverse order. @kbd{M-x
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
500 copy-to-buffer} is similar, except that any existing text in the other
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
501 buffer is deleted, so the buffer is left containing just the text newly
Dave Love <fx@gnu.org>
parents:
diff changeset
502 copied into it.
Dave Love <fx@gnu.org>
parents:
diff changeset
503
38415
80b960104fbd Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents: 38206
diff changeset
504 To retrieve the accumulated text from another buffer, use the
80b960104fbd Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents: 38206
diff changeset
505 command @kbd{M-x insert-buffer}; this too takes @var{buffername} as an
80b960104fbd Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents: 38206
diff changeset
506 argument. It inserts a copy of the whole text in buffer
38745
5464ee1ba8e2 Minor cleanups.
Richard M. Stallman <rms@gnu.org>
parents: 38481
diff changeset
507 @var{buffername} into the current buffer at point, and sets the mark
38415
80b960104fbd Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents: 38206
diff changeset
508 after the inserted text. Alternatively, you can select the other
80b960104fbd Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents: 38206
diff changeset
509 buffer for editing, then copy text from it by killing.
80b960104fbd Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents: 38206
diff changeset
510 @xref{Buffers}, for background information on buffers.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
511
Dave Love <fx@gnu.org>
parents:
diff changeset
512 Instead of accumulating text within Emacs, in a buffer, you can append
Dave Love <fx@gnu.org>
parents:
diff changeset
513 text directly into a file with @kbd{M-x append-to-file}, which takes
Dave Love <fx@gnu.org>
parents:
diff changeset
514 @var{filename} as an argument. It adds the text of the region to the end
Dave Love <fx@gnu.org>
parents:
diff changeset
515 of the specified file. The file is changed immediately on disk.
Dave Love <fx@gnu.org>
parents:
diff changeset
516
Dave Love <fx@gnu.org>
parents:
diff changeset
517 You should use @code{append-to-file} only with files that are
Dave Love <fx@gnu.org>
parents:
diff changeset
518 @emph{not} being visited in Emacs. Using it on a file that you are
Dave Love <fx@gnu.org>
parents:
diff changeset
519 editing in Emacs would change the file behind Emacs's back, which
Dave Love <fx@gnu.org>
parents:
diff changeset
520 can lead to losing some of your editing.
Dave Love <fx@gnu.org>
parents:
diff changeset
521
Dave Love <fx@gnu.org>
parents:
diff changeset
522 @node Rectangles, Registers, Accumulating Text, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
523 @section Rectangles
Dave Love <fx@gnu.org>
parents:
diff changeset
524 @cindex rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
525 @cindex columns (and rectangles)
Dave Love <fx@gnu.org>
parents:
diff changeset
526 @cindex killing rectangular areas of text
Dave Love <fx@gnu.org>
parents:
diff changeset
527
Dave Love <fx@gnu.org>
parents:
diff changeset
528 The rectangle commands operate on rectangular areas of the text: all
Dave Love <fx@gnu.org>
parents:
diff changeset
529 the characters between a certain pair of columns, in a certain range of
Dave Love <fx@gnu.org>
parents:
diff changeset
530 lines. Commands are provided to kill rectangles, yank killed rectangles,
Dave Love <fx@gnu.org>
parents:
diff changeset
531 clear them out, fill them with blanks or text, or delete them. Rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
532 commands are useful with text in multicolumn formats, and for changing
Dave Love <fx@gnu.org>
parents:
diff changeset
533 text into or out of such formats.
Dave Love <fx@gnu.org>
parents:
diff changeset
534
Dave Love <fx@gnu.org>
parents:
diff changeset
535 When you must specify a rectangle for a command to work on, you do it
Dave Love <fx@gnu.org>
parents:
diff changeset
536 by putting the mark at one corner and point at the opposite corner. The
Dave Love <fx@gnu.org>
parents:
diff changeset
537 rectangle thus specified is called the @dfn{region-rectangle} because
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
538 you control it in much the same way as the region is controlled. But
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
539 remember that a given combination of point and mark values can be
Dave Love <fx@gnu.org>
parents:
diff changeset
540 interpreted either as a region or as a rectangle, depending on the
Dave Love <fx@gnu.org>
parents:
diff changeset
541 command that uses them.
Dave Love <fx@gnu.org>
parents:
diff changeset
542
Dave Love <fx@gnu.org>
parents:
diff changeset
543 If point and the mark are in the same column, the rectangle they
Dave Love <fx@gnu.org>
parents:
diff changeset
544 delimit is empty. If they are in the same line, the rectangle is one
Dave Love <fx@gnu.org>
parents:
diff changeset
545 line high. This asymmetry between lines and columns comes about
Dave Love <fx@gnu.org>
parents:
diff changeset
546 because point (and likewise the mark) is between two columns, but within
Dave Love <fx@gnu.org>
parents:
diff changeset
547 a line.
Dave Love <fx@gnu.org>
parents:
diff changeset
548
Dave Love <fx@gnu.org>
parents:
diff changeset
549 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
550 @item C-x r k
49600
23a1cea22d13 Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents: 49330
diff changeset
551 Kill the text of the region-rectangle, saving its contents as the
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
552 ``last killed rectangle'' (@code{kill-rectangle}).
Dave Love <fx@gnu.org>
parents:
diff changeset
553 @item C-x r d
Dave Love <fx@gnu.org>
parents:
diff changeset
554 Delete the text of the region-rectangle (@code{delete-rectangle}).
Dave Love <fx@gnu.org>
parents:
diff changeset
555 @item C-x r y
Dave Love <fx@gnu.org>
parents:
diff changeset
556 Yank the last killed rectangle with its upper left corner at point
Dave Love <fx@gnu.org>
parents:
diff changeset
557 (@code{yank-rectangle}).
Dave Love <fx@gnu.org>
parents:
diff changeset
558 @item C-x r o
Dave Love <fx@gnu.org>
parents:
diff changeset
559 Insert blank space to fill the space of the region-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
560 (@code{open-rectangle}). This pushes the previous contents of the
Dave Love <fx@gnu.org>
parents:
diff changeset
561 region-rectangle rightward.
49330
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
562 @item C-x r c
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
563 Clear the region-rectangle by replacing its contents with spaces
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
564 (@code{clear-rectangle}).
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
565 @item M-x delete-whitespace-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
566 Delete whitespace in each of the lines on the specified rectangle,
Dave Love <fx@gnu.org>
parents:
diff changeset
567 starting from the left edge column of the rectangle.
27749
986871288b53 *** empty log message ***
Gerd Moellmann <gerd@gnu.org>
parents: 25829
diff changeset
568 @item C-x r t @var{string} @key{RET}
37447
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
569 Replace rectangle contents with @var{string} on each line.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
570 (@code{string-rectangle}).
37447
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
571 @item M-x string-insert-rectangle @key{RET} @var{string} @key{RET}
37572
956f7346b171 (Rectangles): Remove redundant and erroneous name of replace-rectangle
Eli Zaretskii <eliz@gnu.org>
parents: 37486
diff changeset
572 Insert @var{string} on each line of the rectangle.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
573 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
574
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
575 The rectangle operations fall into two classes: commands for
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
576 deleting and inserting rectangles, and commands for blank rectangles.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
577
Dave Love <fx@gnu.org>
parents:
diff changeset
578 @kindex C-x r k
Dave Love <fx@gnu.org>
parents:
diff changeset
579 @kindex C-x r d
Dave Love <fx@gnu.org>
parents:
diff changeset
580 @findex kill-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
581 @findex delete-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
582 There are two ways to get rid of the text in a rectangle: you can
Dave Love <fx@gnu.org>
parents:
diff changeset
583 discard the text (delete it) or save it as the ``last killed''
Dave Love <fx@gnu.org>
parents:
diff changeset
584 rectangle. The commands for these two ways are @kbd{C-x r d}
Dave Love <fx@gnu.org>
parents:
diff changeset
585 (@code{delete-rectangle}) and @kbd{C-x r k} (@code{kill-rectangle}). In
Dave Love <fx@gnu.org>
parents:
diff changeset
586 either case, the portion of each line that falls inside the rectangle's
38461
23f63206a867 Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents: 38415
diff changeset
587 boundaries is deleted, causing any following text on the line to
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
588 move left into the gap.
Dave Love <fx@gnu.org>
parents:
diff changeset
589
Dave Love <fx@gnu.org>
parents:
diff changeset
590 Note that ``killing'' a rectangle is not killing in the usual sense; the
Dave Love <fx@gnu.org>
parents:
diff changeset
591 rectangle is not stored in the kill ring, but in a special place that
Dave Love <fx@gnu.org>
parents:
diff changeset
592 can only record the most recent rectangle killed. This is because yanking
Dave Love <fx@gnu.org>
parents:
diff changeset
593 a rectangle is so different from yanking linear text that different yank
Dave Love <fx@gnu.org>
parents:
diff changeset
594 commands have to be used and yank-popping is hard to make sense of.
Dave Love <fx@gnu.org>
parents:
diff changeset
595
Dave Love <fx@gnu.org>
parents:
diff changeset
596 @kindex C-x r y
Dave Love <fx@gnu.org>
parents:
diff changeset
597 @findex yank-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
598 To yank the last killed rectangle, type @kbd{C-x r y}
Dave Love <fx@gnu.org>
parents:
diff changeset
599 (@code{yank-rectangle}). Yanking a rectangle is the opposite of killing
Dave Love <fx@gnu.org>
parents:
diff changeset
600 one. Point specifies where to put the rectangle's upper left corner.
Dave Love <fx@gnu.org>
parents:
diff changeset
601 The rectangle's first line is inserted there, the rectangle's second
38481
33c054df8f9f Add a missing word.
Eli Zaretskii <eliz@gnu.org>
parents: 38461
diff changeset
602 line is inserted at the same horizontal position, but one line
33c054df8f9f Add a missing word.
Eli Zaretskii <eliz@gnu.org>
parents: 38461
diff changeset
603 vertically down, and so on. The number of lines affected is determined
33c054df8f9f Add a missing word.
Eli Zaretskii <eliz@gnu.org>
parents: 38461
diff changeset
604 by the height of the saved rectangle.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
605
Dave Love <fx@gnu.org>
parents:
diff changeset
606 You can convert single-column lists into double-column lists using
Dave Love <fx@gnu.org>
parents:
diff changeset
607 rectangle killing and yanking; kill the second half of the list as a
Dave Love <fx@gnu.org>
parents:
diff changeset
608 rectangle and then yank it beside the first line of the list.
Dave Love <fx@gnu.org>
parents:
diff changeset
609 @xref{Two-Column}, for another way to edit multi-column text.
Dave Love <fx@gnu.org>
parents:
diff changeset
610
Dave Love <fx@gnu.org>
parents:
diff changeset
611 You can also copy rectangles into and out of registers with @kbd{C-x r
Dave Love <fx@gnu.org>
parents:
diff changeset
612 r @var{r}} and @kbd{C-x r i @var{r}}. @xref{RegRect,,Rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
613 Registers}.
Dave Love <fx@gnu.org>
parents:
diff changeset
614
Dave Love <fx@gnu.org>
parents:
diff changeset
615 @kindex C-x r o
Dave Love <fx@gnu.org>
parents:
diff changeset
616 @findex open-rectangle
49330
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
617 @kindex C-x r c
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
618 @findex clear-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
619 There are two commands you can use for making blank rectangles:
49330
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
620 @kbd{C-x r c} (@code{clear-rectangle}) which blanks out existing text,
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
621 and @kbd{C-x r o} (@code{open-rectangle}) which inserts a blank
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
622 rectangle. Clearing a rectangle is equivalent to deleting it and then
99f721b3f74e (Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents: 47200
diff changeset
623 inserting a blank rectangle of the same size.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
624
Dave Love <fx@gnu.org>
parents:
diff changeset
625 @findex delete-whitespace-rectangle
Dave Love <fx@gnu.org>
parents:
diff changeset
626 The command @kbd{M-x delete-whitespace-rectangle} deletes horizontal
Dave Love <fx@gnu.org>
parents:
diff changeset
627 whitespace starting from a particular column. This applies to each of
Dave Love <fx@gnu.org>
parents:
diff changeset
628 the lines in the rectangle, and the column is specified by the left
Dave Love <fx@gnu.org>
parents:
diff changeset
629 edge of the rectangle. The right edge of the rectangle does not make
Dave Love <fx@gnu.org>
parents:
diff changeset
630 any difference to this command.
Dave Love <fx@gnu.org>
parents:
diff changeset
631
Dave Love <fx@gnu.org>
parents:
diff changeset
632 @kindex C-x r t
Dave Love <fx@gnu.org>
parents:
diff changeset
633 @findex string-rectangle
37585
d44c87635f6e (Rectangles): Remove the description of replace-rectangle.
Eli Zaretskii <eliz@gnu.org>
parents: 37572
diff changeset
634 The command @kbd{C-x r t} (@code{string-rectangle}) replaces the
37447
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
635 contents of a region-rectangle with a string on each line. The
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
636 string's width need not be the same as the width of the rectangle. If
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
637 the string's width is less, the text after the rectangle shifts left;
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
638 if the string is wider than the rectangle, the text after the
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
639 rectangle shifts right.
33805
7d3fd66a3ac3 Fix string-rectangle doc.
Dave Love <fx@gnu.org>
parents: 30895
diff changeset
640
37447
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
641 @findex string-insert-rectangle
49600
23a1cea22d13 Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents: 49330
diff changeset
642 The command @kbd{M-x string-insert-rectangle} is similar to
23a1cea22d13 Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents: 49330
diff changeset
643 @code{string-rectangle}, but inserts the string on each line,
37447
0bc52782144f Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents: 37357
diff changeset
644 shifting the original text to the right.
52401
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
645
56810
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
646 @ifnottex
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
647 @lowersections
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
648 @end ifnottex
24bffa640391 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 56692
diff changeset
649
52401
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
650 @ignore
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
651 arch-tag: d8da8f96-0928-449a-816e-ff2d3497866c
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
652 @end ignore