aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2005-02-06 11:19:45 +0000
committerRichard M. Stallman2005-02-06 11:19:45 +0000
commit3423ce024a8863c001245e0d7ebb27c1aee77620 (patch)
treecb4eb3f8f85cf5b36ad5bd1b437183261e8267cf
parent1db81533c348b2da33a4a4ca9b90514acf51561c (diff)
downloademacs-3423ce024a8863c001245e0d7ebb27c1aee77620.tar.gz
emacs-3423ce024a8863c001245e0d7ebb27c1aee77620.zip
(Other Kill Commands): Cleanup.
Delete redundant explanation of kill in read-only buffer. (Yanking): Mention term "copying". (Accumulating Text): Fix typo.
-rw-r--r--man/killing.texi19
1 files changed, 6 insertions, 13 deletions
diff --git a/man/killing.texi b/man/killing.texi
index ba136831adf..51e352dec6b 100644
--- a/man/killing.texi
+++ b/man/killing.texi
@@ -222,10 +222,10 @@ Kill the following balanced expression (@code{kill-sexp}). @xref{Expressions}.
222Kill through the next occurrence of @var{char} (@code{zap-to-char}). 222Kill through the next occurrence of @var{char} (@code{zap-to-char}).
223@end table 223@end table
224 224
225 A kill command which is very general is @kbd{C-w} 225 The most general kill command is @kbd{C-w} (@code{kill-region}),
226(@code{kill-region}), which kills everything between point and the 226which kills everything between point and the mark. With this command,
227mark. With this command, you can kill any contiguous sequence of 227you can kill any contiguous sequence of characters, if you first set
228characters, if you first set the region around them. 228the region around them.
229 229
230@kindex M-z 230@kindex M-z
231@findex zap-to-char 231@findex zap-to-char
@@ -240,13 +240,6 @@ and @kbd{M-d} (@pxref{Words}); balanced expressions, with @kbd{C-M-k}
240(@pxref{Expressions}); and sentences, with @kbd{C-x @key{DEL}} and 240(@pxref{Expressions}); and sentences, with @kbd{C-x @key{DEL}} and
241@kbd{M-k} (@pxref{Sentences}).@refill 241@kbd{M-k} (@pxref{Sentences}).@refill
242 242
243 You can use kill commands in read-only buffers. They don't actually
244change the buffer, and they beep to warn you of that, but they do copy
245the text you tried to kill into the kill ring, so you can yank it into
246other buffers. Most of the kill commands move point across the text
247they copy in this way, so that successive kill commands build up a
248single kill ring entry as usual.
249
250@node Graphical Kill 243@node Graphical Kill
251@subsection Killing on Graphical Terminals 244@subsection Killing on Graphical Terminals
252 245
@@ -289,7 +282,7 @@ Replace text just yanked with an earlier batch of killed text
289(@code{yank-pop}). 282(@code{yank-pop}).
290@item M-w 283@item M-w
291Save region as last killed text without actually killing it 284Save region as last killed text without actually killing it
292(@code{kill-ring-save}). 285(@code{kill-ring-save}). Some systems call this ``copying''.
293@item C-M-w 286@item C-M-w
294Append next kill to last batch of killed text (@code{append-next-kill}). 287Append next kill to last batch of killed text (@code{append-next-kill}).
295@end table 288@end table
@@ -466,7 +459,7 @@ the command @kbd{C-h v kill-ring}.
466 459
467@cindex accumulating scattered text 460@cindex accumulating scattered text
468 Usually we copy or move text by killing it and yanking it, but there 461 Usually we copy or move text by killing it and yanking it, but there
469are other methods convenient for copying one block of text in many 462are other convenient methods for copying one block of text in many
470places, or for copying many scattered blocks of text into one place. To 463places, or for copying many scattered blocks of text into one place. To
471copy one block to many places, store it in a register 464copy one block to many places, store it in a register
472(@pxref{Registers}). Here we describe the commands to accumulate 465(@pxref{Registers}). Here we describe the commands to accumulate