Mercurial > emacs
annotate man/killing.texi @ 74228:6081cf49eb34
(font-lock-mode): "?\ " -> "?\s".
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Mon, 27 Nov 2006 13:50:42 +0000 |
parents | c7e4f78b81a6 |
children | e282f9062d8d 858cb33ae39d |
rev | line source |
---|---|
25829 | 1 @c This is part of the Emacs manual. |
64890
3723093a21fd
Update years in copyright notice; nfc.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
62330
diff
changeset
|
2 @c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2000, 2001, |
68639
dc2d5a6655a3
Update years in copyright notice; nfc.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
68510
diff
changeset
|
3 @c 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. |
25829 | 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 | 7 @chapter Killing and Moving Text |
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 | 24 @section Deletion and Killing |
59272
2d8dd256436f
(Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents:
56899
diff
changeset
|
25 @end iftex |
25829 | 26 |
27 @cindex killing text | |
28 @cindex cutting text | |
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 | 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 | 58 |
25829 | 59 @menu |
60 * Deletion:: Commands for deleting small amounts of text and | |
61 blank areas. | |
62 * Killing by Lines:: How to kill entire lines of text at one time. | |
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. |
70360
f6892919e3c9
(Killing): Say "graphical displays".
Richard M. Stallman <rms@gnu.org>
parents:
69828
diff
changeset
|
65 * Graphical Kill:: The kill ring on graphical displays: |
59272
2d8dd256436f
(Killing): Reorganize section.
Richard M. Stallman <rms@gnu.org>
parents:
56899
diff
changeset
|
66 yanking between applications. |
25829 | 67 @end menu |
68 | |
37486
d7bf0f33e402
Add @need before Deletion node.
Richard M. Stallman <rms@gnu.org>
parents:
37447
diff
changeset
|
69 @need 1500 |
25829 | 70 @node Deletion |
71 @subsection Deletion | |
72 @findex delete-backward-char | |
73 @findex delete-char | |
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 | 79 @table @kbd |
80 @item C-d | |
68260
da161b813076
(Deletion): Upcase @key argument.
Richard M. Stallman <rms@gnu.org>
parents:
67605
diff
changeset
|
81 @itemx @key{DELETE} |
36657
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 |
68260
da161b813076
(Deletion): Upcase @key argument.
Richard M. Stallman <rms@gnu.org>
parents:
67605
diff
changeset
|
83 @key{DELETE} function key (usually located in the edit keypad), Emacs |
36657
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 | 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} |
68510 | 87 Delete previous character (@code{delete-backward-char}). |
25829 | 88 @item M-\ |
89 Delete spaces and tabs around point (@code{delete-horizontal-space}). | |
90 @item M-@key{SPC} | |
91 Delete spaces and tabs around point, leaving one space | |
92 (@code{just-one-space}). | |
93 @item C-x C-o | |
94 Delete blank lines around the current line (@code{delete-blank-lines}). | |
95 @item M-^ | |
96 Join two lines by deleting the intervening newline, along with any | |
97 indentation following it (@code{delete-indentation}). | |
98 @end table | |
99 | |
36725
640fb21a2098
Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents:
36720
diff
changeset
|
100 @kindex DEL |
640fb21a2098
Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents:
36720
diff
changeset
|
101 @kindex C-d |
25829 | 102 The most basic delete commands are @kbd{C-d} (@code{delete-char}) and |
103 @key{DEL} (@code{delete-backward-char}). @kbd{C-d} deletes the | |
104 character after point, the one the cursor is ``on top of.'' This | |
105 doesn't move point. @key{DEL} deletes the character before the cursor, | |
106 and moves point back. You can delete newlines like any other characters | |
107 in the buffer; deleting a newline joins two lines. Actually, @kbd{C-d} | |
108 and @key{DEL} aren't always delete commands; when given arguments, they | |
109 kill instead, since they can erase more than one character this way. | |
110 | |
36725
640fb21a2098
Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents:
36720
diff
changeset
|
111 @kindex BACKSPACE |
640fb21a2098
Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents:
36720
diff
changeset
|
112 @kindex BS |
640fb21a2098
Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents:
36720
diff
changeset
|
113 @kindex DELETE |
68510 | 114 Every keyboard has a large key which is a short distance above the |
36725
640fb21a2098
Clarify the text for BACKSPACE vs DELETE.
Richard M. Stallman <rms@gnu.org>
parents:
36720
diff
changeset
|
115 @key{RET} or @key{ENTER} key and is normally used for erasing what you |
68510 | 116 have typed. It may be labeled @key{DEL}, @key{BACKSPACE}, @key{BS}, |
117 @key{DELETE}, or even with a left arrow. Regardless of the label on | |
118 the key, in Emacs it called @key{DEL}, and it should delete one | |
119 character backwards. | |
36725
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 |
68708
c0833efdd110
"Graphical display", not window system.
Richard M. Stallman <rms@gnu.org>
parents:
68639
diff
changeset
|
128 graphical display, 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 | 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 | 144 @kindex M-\ |
145 @findex delete-horizontal-space | |
146 @kindex M-SPC | |
147 @findex just-one-space | |
148 The other delete commands are those which delete only whitespace | |
149 characters: spaces, tabs and newlines. @kbd{M-\} | |
150 (@code{delete-horizontal-space}) deletes all the spaces and tab | |
151 characters before and after point. @kbd{M-@key{SPC}} | |
152 (@code{just-one-space}) does likewise but leaves a single space after | |
153 point, regardless of the number of spaces that existed previously (even | |
60795
45dee811cbe6
(Deletion): Document numeric argument for just-one-space.
Richard M. Stallman <rms@gnu.org>
parents:
59951
diff
changeset
|
154 if there were none before). With a numeric argument @var{n}, it |
45dee811cbe6
(Deletion): Document numeric argument for just-one-space.
Richard M. Stallman <rms@gnu.org>
parents:
59951
diff
changeset
|
155 leaves @var{n} spaces after point. |
25829 | 156 |
157 @kbd{C-x C-o} (@code{delete-blank-lines}) deletes all blank lines | |
158 after the current line. If the current line is blank, it deletes all | |
159 blank lines preceding the current line as well (leaving one blank line, | |
62330
747b2c665140
(Deletion): Complete description of `C-x C-o'.
Luc Teirlinck <teirllm@auburn.edu>
parents:
60795
diff
changeset
|
160 the current line). On a solitary blank line, it deletes that line. |
25829 | 161 |
162 @kbd{M-^} (@code{delete-indentation}) joins the current line and the | |
163 previous line, by deleting a newline and all surrounding spaces, usually | |
164 leaving a single space. @xref{Indentation,M-^}. | |
165 | |
166 @node Killing by Lines | |
167 @subsection Killing by Lines | |
168 | |
169 @table @kbd | |
170 @item C-k | |
171 Kill rest of line or one or more lines (@code{kill-line}). | |
67605
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
172 @item C-S-backspace |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
173 Kill an entire line at once (@code{kill-whole-line}) |
25829 | 174 @end table |
175 | |
176 @kindex C-k | |
177 @findex kill-line | |
178 The simplest kill command is @kbd{C-k}. If given at the beginning of | |
179 a line, it kills all the text on the line, leaving it blank. When used | |
180 on a blank line, it kills the whole line including its newline. To kill | |
181 an entire non-blank line, go to the beginning and type @kbd{C-k} twice. | |
182 | |
183 More generally, @kbd{C-k} kills from point up to the end of the line, | |
184 unless it is at the end of a line. In that case it kills the newline | |
185 following point, thus merging the next line into the current one. | |
186 Spaces and tabs that you can't see at the end of the line are ignored | |
187 when deciding which case applies, so if point appears to be at the end | |
188 of the line, you can be sure @kbd{C-k} will kill the newline. | |
189 | |
190 When @kbd{C-k} is given a positive argument, it kills that many lines | |
191 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
|
192 before point is not killed). With a negative argument @minus{}@var{n}, it |
25829 | 193 kills @var{n} lines preceding the current line (together with the text |
194 on the current line before point). Thus, @kbd{C-u - 2 C-k} at the front | |
195 of a line kills the two previous lines. | |
196 | |
197 @kbd{C-k} with an argument of zero kills the text before point on the | |
198 current line. | |
199 | |
200 @vindex kill-whole-line | |
201 If the variable @code{kill-whole-line} is non-@code{nil}, @kbd{C-k} at | |
202 the very beginning of a line kills the entire line including the | |
203 following newline. This variable is normally @code{nil}. | |
204 | |
67605
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
205 @kindex C-S-backspace |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
206 @findex kill-whole-line |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
207 @kbd{C-S-backspace} (@code{kill-whole-line}) will kill a whole line |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
208 including its newline regardless of the position of point within the |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
209 line. Note that many character terminals will prevent you from typing |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
210 the key sequence @kbd{C-S-backspace}. |
d16a1283eb9b
(Killing by Lines): Document `kill-whole-line' function.
Eli Zaretskii <eliz@gnu.org>
parents:
67434
diff
changeset
|
211 |
25829 | 212 @node Other Kill Commands |
213 @subsection Other Kill Commands | |
214 @findex kill-region | |
215 @kindex C-w | |
216 | |
217 @table @kbd | |
218 @item C-w | |
219 Kill region (from point to the mark) (@code{kill-region}). | |
220 @item M-d | |
221 Kill word (@code{kill-word}). @xref{Words}. | |
222 @item M-@key{DEL} | |
223 Kill word backwards (@code{backward-kill-word}). | |
224 @item C-x @key{DEL} | |
225 Kill back to beginning of sentence (@code{backward-kill-sentence}). | |
226 @xref{Sentences}. | |
227 @item M-k | |
228 Kill to end of sentence (@code{kill-sentence}). | |
229 @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
|
230 Kill the following balanced expression (@code{kill-sexp}). @xref{Expressions}. |
25829 | 231 @item M-z @var{char} |
232 Kill through the next occurrence of @var{char} (@code{zap-to-char}). | |
233 @end table | |
234 | |
59951
c2c2b868b75f
(Other Kill Commands): Cleanup.
Richard M. Stallman <rms@gnu.org>
parents:
59284
diff
changeset
|
235 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
|
236 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
|
237 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
|
238 the region around them. |
25829 | 239 |
240 @kindex M-z | |
241 @findex zap-to-char | |
242 A convenient way of killing is combined with searching: @kbd{M-z} | |
243 (@code{zap-to-char}) reads a character and kills from point up to (and | |
244 including) the next occurrence of that character in the buffer. A | |
245 numeric argument acts as a repeat count. A negative argument means to | |
246 search backward and kill text before point. | |
247 | |
38206
b13ab91e3dd8
Say "expression" instead of "sexp". Update xref, Sexps -> Expressions.
Richard M. Stallman <rms@gnu.org>
parents:
37887
diff
changeset
|
248 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
|
249 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
|
250 (@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
|
251 @kbd{M-k} (@pxref{Sentences}).@refill |
25829 | 252 |
59284
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
253 @node Graphical Kill |
68510 | 254 @subsection Killing on Graphical Displays |
59284
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
255 |
68510 | 256 On graphical displays with window systems, the most recent kill done |
257 in Emacs is also the primary selection, if it is more recent than any | |
258 selection you made in another program. This means that the paste | |
259 commands of other window-based applications copy the text that you | |
260 killed in Emacs. In addition, Emacs yank commands treat other | |
261 applications' selections as part of the kill ring, so you can yank | |
262 them into Emacs. | |
59284
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
263 |
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
264 @cindex Delete Selection mode |
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
265 @cindex mode, Delete Selection |
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
266 @findex delete-selection-mode |
68708
c0833efdd110
"Graphical display", not window system.
Richard M. Stallman <rms@gnu.org>
parents:
68639
diff
changeset
|
267 Many graphical applications follow the convention that insertion while text |
59284
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
268 is selected deletes the selected text. You can make Emacs behave this |
68510 | 269 way by enabling Delete Selection mode---with @kbd{M-x |
270 delete-selection-mode} or using Custom. Another effect of this mode | |
59284
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
271 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
|
272 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
|
273 mode (@pxref{Transient Mark}). |
54ff1fbcac20
(Graphical Kill): Move up under node Killing,
Andreas Schwab <schwab@suse.de>
parents:
59272
diff
changeset
|
274 |
25829 | 275 @node Yanking, Accumulating Text, Killing, Top |
276 @section Yanking | |
277 @cindex moving text | |
278 @cindex copying text | |
279 @cindex kill ring | |
280 @cindex yanking | |
281 @cindex pasting | |
282 | |
283 @dfn{Yanking} means reinserting text previously killed. This is what | |
284 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
|
285 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
|
286 because Emacs remembers many recent kills, not just the last one. |
25829 | 287 |
288 @table @kbd | |
289 @item C-y | |
290 Yank last killed text (@code{yank}). | |
291 @item M-y | |
292 Replace text just yanked with an earlier batch of killed text | |
293 (@code{yank-pop}). | |
294 @item M-w | |
295 Save region as last killed text without actually killing it | |
72101
c7e4f78b81a6
Move periods and commas inside quotes.
Richard M. Stallman <rms@gnu.org>
parents:
71751
diff
changeset
|
296 (@code{kill-ring-save}). Some systems call this ``copying.'' |
25829 | 297 @item C-M-w |
298 Append next kill to last batch of killed text (@code{append-next-kill}). | |
299 @end table | |
300 | |
68510 | 301 On graphical displays with window systems, if there is a current |
302 selection in some other application, and you selected it more recently | |
303 than you killed any text in Emacs, @kbd{C-y} copies the selection | |
304 instead of text killed within Emacs. | |
46037
7af49c69e77b
Mention that kill commands communicate with other apps,
Richard M. Stallman <rms@gnu.org>
parents:
39264
diff
changeset
|
305 |
25829 | 306 @menu |
307 * Kill Ring:: Where killed text is stored. Basic yanking. | |
308 * Appending Kills:: Several kills in a row all yank together. | |
309 * Earlier Kills:: Yanking something killed some time ago. | |
310 @end menu | |
311 | |
312 @node Kill Ring | |
313 @subsection The Kill Ring | |
314 | |
315 All killed text is recorded in the @dfn{kill ring}, a list of blocks of | |
316 text that have been killed. There is only one kill ring, shared by all | |
317 buffers, so you can kill text in one buffer and yank it in another buffer. | |
318 This is the usual way to move text from one file to another. | |
319 (@xref{Accumulating Text}, for some other ways.) | |
320 | |
321 @kindex C-y | |
322 @findex yank | |
323 The command @kbd{C-y} (@code{yank}) reinserts the text of the most recent | |
324 kill. It leaves the cursor at the end of the text. It sets the mark at | |
325 the beginning of the text. @xref{Mark}. | |
326 | |
327 @kbd{C-u C-y} leaves the cursor in front of the text, and sets the | |
328 mark after it. This happens only if the argument is specified with just | |
329 a @kbd{C-u}, precisely. Any other sort of argument, including @kbd{C-u} | |
330 and digits, specifies an earlier kill to yank (@pxref{Earlier Kills}). | |
331 | |
46241
0ed85ef15043
Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents:
46037
diff
changeset
|
332 @cindex yanking and text properties |
0ed85ef15043
Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents:
46037
diff
changeset
|
333 @vindex yank-excluded-properties |
0ed85ef15043
Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents:
46037
diff
changeset
|
334 The yank commands discard certain text properties from the text that |
47200 | 335 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
|
336 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
|
337 bindings. The variable @code{yank-excluded-properties} specifies the |
0ed85ef15043
Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents:
46037
diff
changeset
|
338 properties to discard. Yanking of register contents and rectangles |
0ed85ef15043
Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents:
46037
diff
changeset
|
339 also discard these properties. |
0ed85ef15043
Describe yank-excluded-properties.
Richard M. Stallman <rms@gnu.org>
parents:
46037
diff
changeset
|
340 |
25829 | 341 @kindex M-w |
342 @findex kill-ring-save | |
343 To copy a block of text, you can use @kbd{M-w} | |
344 (@code{kill-ring-save}), which copies the region into the kill ring | |
345 without removing it from the buffer. This is approximately equivalent | |
346 to @kbd{C-w} followed by @kbd{C-x u}, except that @kbd{M-w} does not | |
347 alter the undo history and does not temporarily change the screen. | |
348 | |
349 @node Appending Kills | |
350 @subsection Appending Kills | |
351 | |
352 @cindex appending kills in the ring | |
353 @cindex television | |
354 Normally, each kill command pushes a new entry onto the kill ring. | |
355 However, two or more kill commands in a row combine their text into a | |
356 single entry, so that a single @kbd{C-y} yanks all the text as a unit, | |
357 just as it was before it was killed. | |
358 | |
359 Thus, if you want to yank text as a unit, you need not kill all of it | |
360 with one command; you can keep killing line after line, or word after | |
361 word, until you have killed it all, and you can still get it all back at | |
362 once. | |
363 | |
364 Commands that kill forward from point add onto the end of the previous | |
365 killed text. Commands that kill backward from point add text onto the | |
366 beginning. This way, any sequence of mixed forward and backward kill | |
367 commands puts all the killed text into one entry without rearrangement. | |
368 Numeric arguments do not break the sequence of appending kills. For | |
369 example, suppose the buffer contains this text: | |
370 | |
371 @example | |
372 This is a line @point{}of sample text. | |
373 @end example | |
374 | |
375 @noindent | |
376 with point shown by @point{}. If you type @kbd{M-d M-@key{DEL} M-d | |
377 M-@key{DEL}}, killing alternately forward and backward, you end up with | |
378 @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
|
379 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
|
380 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
|
381 @kbd{M-q}.) |
25829 | 382 |
383 Another way to kill the same text is to move back two words with | |
384 @kbd{M-b M-b}, then kill all four words forward with @kbd{C-u M-d}. | |
385 This produces exactly the same results in the buffer and in the kill | |
386 ring. @kbd{M-f M-f C-u M-@key{DEL}} kills the same text, all going | |
387 backward; once again, the result is the same. The text in the kill ring | |
388 entry always has the same order that it had in the buffer before you | |
389 killed it. | |
390 | |
391 @kindex C-M-w | |
392 @findex append-next-kill | |
393 If a kill command is separated from the last kill command by other | |
394 commands (not just numeric arguments), it starts a new entry on the kill | |
395 ring. But you can force it to append by first typing the command | |
396 @kbd{C-M-w} (@code{append-next-kill}) right before it. The @kbd{C-M-w} | |
397 tells the following command, if it is a kill command, to append the text | |
398 it kills to the last killed text, instead of starting a new entry. With | |
399 @kbd{C-M-w}, you can kill several separated pieces of text and | |
400 accumulate them to be yanked back in one place.@refill | |
401 | |
402 A kill command following @kbd{M-w} does not append to the text that | |
403 @kbd{M-w} copied into the kill ring. | |
404 | |
405 @node Earlier Kills | |
406 @subsection Yanking Earlier Kills | |
407 | |
408 @cindex yanking previous kills | |
409 @kindex M-y | |
410 @findex yank-pop | |
411 To recover killed text that is no longer the most recent kill, use the | |
412 @kbd{M-y} command (@code{yank-pop}). It takes the text previously | |
413 yanked and replaces it with the text from an earlier kill. So, to | |
414 recover the text of the next-to-the-last kill, first use @kbd{C-y} to | |
415 yank the last kill, and then use @kbd{M-y} to replace it with the | |
416 previous kill. @kbd{M-y} is allowed only after a @kbd{C-y} or another | |
417 @kbd{M-y}. | |
418 | |
419 You can understand @kbd{M-y} in terms of a ``last yank'' pointer which | |
420 points at an entry in the kill ring. Each time you kill, the ``last | |
421 yank'' pointer moves to the newly made entry at the front of the ring. | |
422 @kbd{C-y} yanks the entry which the ``last yank'' pointer points to. | |
423 @kbd{M-y} moves the ``last yank'' pointer to a different entry, and the | |
424 text in the buffer changes to match. Enough @kbd{M-y} commands can move | |
425 the pointer to any entry in the ring, so you can get any entry into the | |
426 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
|
427 @kbd{M-y} loops back around to the first entry again. |
25829 | 428 |
429 @kbd{M-y} moves the ``last yank'' pointer around the ring, but it does | |
430 not change the order of the entries in the ring, which always runs from | |
431 the most recent kill at the front to the oldest one still remembered. | |
432 | |
433 @kbd{M-y} can take a numeric argument, which tells it how many entries | |
434 to advance the ``last yank'' pointer by. A negative argument moves the | |
435 pointer toward the front of the ring; from the front of the ring, it | |
436 moves ``around'' to the last entry and continues forward from there. | |
437 | |
438 Once the text you are looking for is brought into the buffer, you can | |
439 stop doing @kbd{M-y} commands and it will stay there. It's just a copy | |
440 of the kill ring entry, so editing it in the buffer does not change | |
441 what's in the ring. As long as no new killing is done, the ``last | |
442 yank'' pointer remains at the same place in the kill ring, so repeating | |
443 @kbd{C-y} will yank another copy of the same previous kill. | |
444 | |
38745 | 445 If you know how many @kbd{M-y} commands it would take to find the |
446 text you want, you can yank that text in one step using @kbd{C-y} with | |
447 a numeric argument. @kbd{C-y} with an argument restores the text from | |
448 the specified kill ring entry, counting back from the most recent as | |
449 1. Thus, @kbd{C-u 2 C-y} gets the next-to-the-last block of killed | |
450 text---it is equivalent to @kbd{C-y M-y}. @kbd{C-y} with a numeric | |
451 argument starts counting from the ``last yank'' pointer, and sets the | |
452 ``last yank'' pointer to the entry that it yanks. | |
25829 | 453 |
454 @vindex kill-ring-max | |
455 The length of the kill ring is controlled by the variable | |
456 @code{kill-ring-max}; no more than that many blocks of killed text are | |
457 saved. | |
458 | |
459 @vindex kill-ring | |
460 The actual contents of the kill ring are stored in a variable named | |
461 @code{kill-ring}; you can view the entire contents of the kill ring with | |
462 the command @kbd{C-h v kill-ring}. | |
463 | |
464 @node Accumulating Text, Rectangles, Yanking, Top | |
465 @section Accumulating Text | |
466 @findex append-to-buffer | |
467 @findex prepend-to-buffer | |
468 @findex copy-to-buffer | |
469 @findex append-to-file | |
470 | |
471 @cindex accumulating scattered text | |
472 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
|
473 are other convenient methods for copying one block of text in many |
25829 | 474 places, or for copying many scattered blocks of text into one place. To |
475 copy one block to many places, store it in a register | |
476 (@pxref{Registers}). Here we describe the commands to accumulate | |
477 scattered pieces of text into a buffer or into a file. | |
478 | |
479 @table @kbd | |
480 @item M-x append-to-buffer | |
38745 | 481 Append region to the contents of a specified buffer. |
25829 | 482 @item M-x prepend-to-buffer |
38745 | 483 Prepend region to the contents of a specified buffer. |
25829 | 484 @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
|
485 Copy region into a specified buffer, deleting that buffer's old contents. |
25829 | 486 @item M-x insert-buffer |
38745 | 487 Insert the contents of a specified buffer into current buffer at point. |
25829 | 488 @item M-x append-to-file |
38745 | 489 Append region to the contents of a specified file, at the end. |
25829 | 490 @end table |
491 | |
492 To accumulate text into a buffer, use @kbd{M-x append-to-buffer}. | |
493 This reads a buffer name, then inserts a copy of the region into the | |
494 buffer specified. If you specify a nonexistent buffer, | |
495 @code{append-to-buffer} creates the buffer. The text is inserted | |
496 wherever point is in that buffer. If you have been using the buffer for | |
497 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
|
498 starting from wherever point happens to be at that moment. |
25829 | 499 |
500 Point in that buffer is left at the end of the copied text, so | |
501 successive uses of @code{append-to-buffer} accumulate the text in the | |
502 specified buffer in the same order as they were copied. Strictly | |
503 speaking, @code{append-to-buffer} does not always append to the text | |
504 already in the buffer---it appends only if point in that buffer is at the end. | |
505 However, if @code{append-to-buffer} is the only command you use to alter | |
506 a buffer, then point is always at the end. | |
507 | |
508 @kbd{M-x prepend-to-buffer} is just like @code{append-to-buffer} | |
509 except that point in the other buffer is left before the copied text, so | |
510 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
|
511 copy-to-buffer} is similar, except that any existing text in the other |
25829 | 512 buffer is deleted, so the buffer is left containing just the text newly |
513 copied into it. | |
514 | |
38415
80b960104fbd
Minor clarification about insert-buffer.
Richard M. Stallman <rms@gnu.org>
parents:
38206
diff
changeset
|
515 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
|
516 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
|
517 argument. It inserts a copy of the whole text in buffer |
38745 | 518 @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
|
519 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
|
520 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
|
521 @xref{Buffers}, for background information on buffers. |
25829 | 522 |
523 Instead of accumulating text within Emacs, in a buffer, you can append | |
524 text directly into a file with @kbd{M-x append-to-file}, which takes | |
525 @var{filename} as an argument. It adds the text of the region to the end | |
526 of the specified file. The file is changed immediately on disk. | |
527 | |
528 You should use @code{append-to-file} only with files that are | |
529 @emph{not} being visited in Emacs. Using it on a file that you are | |
530 editing in Emacs would change the file behind Emacs's back, which | |
531 can lead to losing some of your editing. | |
532 | |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
533 @node Rectangles, CUA Bindings, Accumulating Text, Top |
25829 | 534 @section Rectangles |
535 @cindex rectangle | |
536 @cindex columns (and rectangles) | |
537 @cindex killing rectangular areas of text | |
538 | |
539 The rectangle commands operate on rectangular areas of the text: all | |
540 the characters between a certain pair of columns, in a certain range of | |
541 lines. Commands are provided to kill rectangles, yank killed rectangles, | |
542 clear them out, fill them with blanks or text, or delete them. Rectangle | |
543 commands are useful with text in multicolumn formats, and for changing | |
544 text into or out of such formats. | |
545 | |
69828
4d337f37e313
(Rectangles): Add index entry for marking a rectangle.
Eli Zaretskii <eliz@gnu.org>
parents:
68708
diff
changeset
|
546 @cindex mark rectangle |
25829 | 547 When you must specify a rectangle for a command to work on, you do it |
548 by putting the mark at one corner and point at the opposite corner. The | |
549 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
|
550 you control it in much the same way as the region is controlled. But |
25829 | 551 remember that a given combination of point and mark values can be |
552 interpreted either as a region or as a rectangle, depending on the | |
553 command that uses them. | |
554 | |
555 If point and the mark are in the same column, the rectangle they | |
556 delimit is empty. If they are in the same line, the rectangle is one | |
557 line high. This asymmetry between lines and columns comes about | |
558 because point (and likewise the mark) is between two columns, but within | |
559 a line. | |
560 | |
561 @table @kbd | |
562 @item C-x r k | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
49330
diff
changeset
|
563 Kill the text of the region-rectangle, saving its contents as the |
25829 | 564 ``last killed rectangle'' (@code{kill-rectangle}). |
565 @item C-x r d | |
566 Delete the text of the region-rectangle (@code{delete-rectangle}). | |
567 @item C-x r y | |
568 Yank the last killed rectangle with its upper left corner at point | |
569 (@code{yank-rectangle}). | |
570 @item C-x r o | |
571 Insert blank space to fill the space of the region-rectangle | |
572 (@code{open-rectangle}). This pushes the previous contents of the | |
573 region-rectangle rightward. | |
49330
99f721b3f74e
(Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents:
47200
diff
changeset
|
574 @item C-x r c |
99f721b3f74e
(Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents:
47200
diff
changeset
|
575 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
|
576 (@code{clear-rectangle}). |
25829 | 577 @item M-x delete-whitespace-rectangle |
578 Delete whitespace in each of the lines on the specified rectangle, | |
579 starting from the left edge column of the rectangle. | |
27749 | 580 @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
|
581 Replace rectangle contents with @var{string} on each line. |
25829 | 582 (@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
|
583 @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
|
584 Insert @var{string} on each line of the rectangle. |
25829 | 585 @end table |
586 | |
38461
23f63206a867
Proofreading fixes from Chris Green <chris_e_green@yahoo.com>.
Eli Zaretskii <eliz@gnu.org>
parents:
38415
diff
changeset
|
587 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
|
588 deleting and inserting rectangles, and commands for blank rectangles. |
25829 | 589 |
590 @kindex C-x r k | |
591 @kindex C-x r d | |
592 @findex kill-rectangle | |
593 @findex delete-rectangle | |
594 There are two ways to get rid of the text in a rectangle: you can | |
595 discard the text (delete it) or save it as the ``last killed'' | |
596 rectangle. The commands for these two ways are @kbd{C-x r d} | |
597 (@code{delete-rectangle}) and @kbd{C-x r k} (@code{kill-rectangle}). In | |
598 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
|
599 boundaries is deleted, causing any following text on the line to |
25829 | 600 move left into the gap. |
601 | |
602 Note that ``killing'' a rectangle is not killing in the usual sense; the | |
603 rectangle is not stored in the kill ring, but in a special place that | |
604 can only record the most recent rectangle killed. This is because yanking | |
605 a rectangle is so different from yanking linear text that different yank | |
68510 | 606 commands have to be used. It is hard to define yank-popping for rectangles, |
607 so we do not try. | |
25829 | 608 |
609 @kindex C-x r y | |
610 @findex yank-rectangle | |
611 To yank the last killed rectangle, type @kbd{C-x r y} | |
612 (@code{yank-rectangle}). Yanking a rectangle is the opposite of killing | |
613 one. Point specifies where to put the rectangle's upper left corner. | |
614 The rectangle's first line is inserted there, the rectangle's second | |
38481 | 615 line is inserted at the same horizontal position, but one line |
616 vertically down, and so on. The number of lines affected is determined | |
617 by the height of the saved rectangle. | |
25829 | 618 |
619 You can convert single-column lists into double-column lists using | |
620 rectangle killing and yanking; kill the second half of the list as a | |
621 rectangle and then yank it beside the first line of the list. | |
622 @xref{Two-Column}, for another way to edit multi-column text. | |
623 | |
624 You can also copy rectangles into and out of registers with @kbd{C-x r | |
625 r @var{r}} and @kbd{C-x r i @var{r}}. @xref{RegRect,,Rectangle | |
626 Registers}. | |
627 | |
628 @kindex C-x r o | |
629 @findex open-rectangle | |
49330
99f721b3f74e
(Rectangles): Document C-x c r.
Richard M. Stallman <rms@gnu.org>
parents:
47200
diff
changeset
|
630 @kindex C-x r c |
25829 | 631 @findex clear-rectangle |
632 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
|
633 @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
|
634 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
|
635 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
|
636 inserting a blank rectangle of the same size. |
25829 | 637 |
638 @findex delete-whitespace-rectangle | |
639 The command @kbd{M-x delete-whitespace-rectangle} deletes horizontal | |
640 whitespace starting from a particular column. This applies to each of | |
641 the lines in the rectangle, and the column is specified by the left | |
642 edge of the rectangle. The right edge of the rectangle does not make | |
643 any difference to this command. | |
644 | |
645 @kindex C-x r t | |
646 @findex string-rectangle | |
37585
d44c87635f6e
(Rectangles): Remove the description of replace-rectangle.
Eli Zaretskii <eliz@gnu.org>
parents:
37572
diff
changeset
|
647 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
|
648 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
|
649 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
|
650 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
|
651 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
|
652 rectangle shifts right. |
33805 | 653 |
37447
0bc52782144f
Adapt to the change of string-rectangle back to 20.x behaviour.
Gerd Moellmann <gerd@gnu.org>
parents:
37357
diff
changeset
|
654 @findex string-insert-rectangle |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
49330
diff
changeset
|
655 The command @kbd{M-x string-insert-rectangle} is similar to |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
49330
diff
changeset
|
656 @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
|
657 shifting the original text to the right. |
52401 | 658 |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
659 @node CUA Bindings, Registers, Rectangles, Top |
66787
0d11e9f86005
(CUA Bindings): Add @section.
Luc Teirlinck <teirllm@auburn.edu>
parents:
66782
diff
changeset
|
660 @section CUA Bindings |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
661 @findex cua-mode |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
662 @vindex cua-mode |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
663 @cindex CUA key bindings |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
664 @vindex cua-enable-cua-keys |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
665 The command @kbd{M-x cua-mode} sets up key bindings that are |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
666 compatible with the Common User Access (CUA) system used in many other |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
667 applications. @kbd{C-x} means cut (kill), @kbd{C-c} copy, @kbd{C-v} |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
668 paste (yank), and @kbd{C-z} undo. Standard Emacs commands like |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
669 @kbd{C-x C-c} still work, because @kbd{C-x} and @kbd{C-c} only take |
67434
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
670 effect when the mark is active (and the region is highlighted). |
68510 | 671 However, if you don't want to override these bindings Emacs at all, set |
67434
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
672 @code{cua-enable-cua-keys} to @code{nil}. |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
673 |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
674 In CUA mode, using @kbd{Shift} together with the movement keys |
67434
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
675 activates and highlights the region over which they move. The |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
676 standard (unshifted) movement keys deactivate the mark, and typed text |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
677 replaces the active region as in Delete-Selection mode |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
678 (@pxref{Graphical Kill}). |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
679 |
68510 | 680 To enter an Emacs command like @kbd{C-x C-f} while the mark is |
681 active, use one of the following methods: either hold @kbd{Shift} | |
682 together with the prefix key, e.g. @kbd{S-C-x C-f}, or quickly type | |
683 the prefix key twice, e.g. @kbd{C-x C-x C-f}. | |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
684 |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
685 @cindex rectangle highlighting |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
686 CUA mode provides enhanced rectangle support with visible |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
687 rectangle highlighting. Use @kbd{C-RET} to start a rectangle, |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
688 extend it using the movement commands, and cut or copy it using |
67434
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
689 @kbd{C-x} or @kbd{C-c}. @kbd{RET} moves the cursor to the next |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
690 (clockwise) corner of the rectangle, so you can easily expand it in |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
691 any direction. Normal text you type is inserted to the left or right |
6d3669227452
(CUA Bindings): Describe how to use C-x and C-c as
Kim F. Storm <storm@cua.dk>
parents:
66787
diff
changeset
|
692 of each line in the rectangle (on the same side as the cursor). |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
693 |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
694 With CUA you can easily copy text and rectangles into and out of |
71751 | 695 registers by providing a one-digit numeric prefix to the kill, copy, |
66782
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
696 and yank commands, e.g. @kbd{C-1 C-c} copies the region into register |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
697 @code{1}, and @kbd{C-2 C-v} yanks the contents of register @code{2}. |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
698 |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
699 @cindex global mark |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
700 CUA mode also has a global mark feature which allows easy moving and |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
701 copying of text between buffers. Use @kbd{C-S-SPC} to toggle the |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
702 global mark on and off. When the global mark is on, all text that you |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
703 kill or copy is automatically inserted at the global mark, and text |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
704 you type is inserted at the global mark rather than at the current |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
705 position. |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
706 |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
707 For example, to copy words from various buffers into a word list in |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
708 a given buffer, set the global mark in the target buffer, then |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
709 navigate to each of the words you want in the list, mark it (e.g. with |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
710 @kbd{S-M-f}), copy it to the list with @kbd{C-c} or @kbd{M-w}, and |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
711 insert a newline after the word in the target list by pressing |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
712 @key{RET}. |
e30f43430f3c
* killing.texi (CUA Bindings): New node. Moved here from
Kim F. Storm <storm@cua.dk>
parents:
64890
diff
changeset
|
713 |
56810
24bffa640391
Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents:
56692
diff
changeset
|
714 @ifnottex |
24bffa640391
Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents:
56692
diff
changeset
|
715 @lowersections |
24bffa640391
Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents:
56692
diff
changeset
|
716 @end ifnottex |
24bffa640391
Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents:
56692
diff
changeset
|
717 |
52401 | 718 @ignore |
719 arch-tag: d8da8f96-0928-449a-816e-ff2d3497866c | |
720 @end ignore |