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