aboutsummaryrefslogtreecommitdiffstats
path: root/man/killing.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>2005-02-06 11:19:45 +0000
committerRichard M. Stallman <[email protected]>2005-02-06 11:19:45 +0000
commit3423ce024a8863c001245e0d7ebb27c1aee77620 (patch)
treecb4eb3f8f85cf5b36ad5bd1b437183261e8267cf /man/killing.texi
parent1db81533c348b2da33a4a4ca9b90514acf51561c (diff)
(Other Kill Commands): Cleanup.
Delete redundant explanation of kill in read-only buffer. (Yanking): Mention term "copying". (Accumulating Text): Fix typo.
Diffstat (limited to 'man/killing.texi')
-rw-r--r--man/killing.texi19
1 files changed, 6 insertions, 13 deletions
diff --git a/man/killing.texi b/man/killing.texi
index ba136831ad..51e352dec6 100644
--- a/man/killing.texi
+++ b/man/killing.texi
@@ -222,10 +222,10 @@ Kill the following balanced expression (@code{kill-sexp}). @xref{Expressions}.
Kill through the next occurrence of @var{char} (@code{zap-to-char}).
@end table
- A kill command which is very general is @kbd{C-w}
-(@code{kill-region}), which kills everything between point and the
-mark. With this command, you can kill any contiguous sequence of
-characters, if you first set the region around them.
+ The most general kill command is @kbd{C-w} (@code{kill-region}),
+which kills everything between point and the mark. With this command,
+you can kill any contiguous sequence of characters, if you first set
+the region around them.
@kindex M-z
@findex zap-to-char
@@ -240,13 +240,6 @@ and @kbd{M-d} (@pxref{Words}); balanced expressions, with @kbd{C-M-k}
(@pxref{Expressions}); and sentences, with @kbd{C-x @key{DEL}} and
@kbd{M-k} (@pxref{Sentences}).@refill
- You can use kill commands in read-only buffers. They don't actually
-change the buffer, and they beep to warn you of that, but they do copy
-the text you tried to kill into the kill ring, so you can yank it into
-other buffers. Most of the kill commands move point across the text
-they copy in this way, so that successive kill commands build up a
-single kill ring entry as usual.
-
@node Graphical Kill
@subsection Killing on Graphical Terminals
@@ -289,7 +282,7 @@ Replace text just yanked with an earlier batch of killed text
(@code{yank-pop}).
@item M-w
Save region as last killed text without actually killing it
-(@code{kill-ring-save}).
+(@code{kill-ring-save}). Some systems call this ``copying''.
@item C-M-w
Append next kill to last batch of killed text (@code{append-next-kill}).
@end table
@@ -466,7 +459,7 @@ the command @kbd{C-h v kill-ring}.
@cindex accumulating scattered text
Usually we copy or move text by killing it and yanking it, but there
-are other methods convenient for copying one block of text in many
+are other convenient methods for copying one block of text in many
places, or for copying many scattered blocks of text into one place. To
copy one block to many places, store it in a register
(@pxref{Registers}). Here we describe the commands to accumulate