[Emacs-diffs] trunk r115567: * killing.texi (Appending Kills): Note that append-next-kill can prepend the kill.

[Chong Yidong]

------------------------------------------------------------
revno: 115567
revision-id: address@hidden
parent: address@hidden
committer: Chong Yidong <address@hidden>
branch nick: trunk
timestamp: Tue 2013-12-17 23:57:38 +0800
message:
  * killing.texi (Appending Kills): Note that append-next-kill can prepend the 
kill.
modified:
  doc/emacs/ChangeLog            changelog-20091113204419-o5vbwnq5f7feedwu-6227
  doc/emacs/killing.texi         
killing.texi-20091113204419-o5vbwnq5f7feedwu-6258

=== modified file 'doc/emacs/ChangeLog'
--- a/doc/emacs/ChangeLog       2013-12-12 18:19:10 +0000
+++ b/doc/emacs/ChangeLog       2013-12-17 15:57:38 +0000
@@ -1,3 +1,8 @@
+2013-12-17  Chong Yidong  <address@hidden>
+
+       * killing.texi (Appending Kills): Note that append-next-kill can
+       prepend the kill.
+
 2013-12-12  Eli Zaretskii  <address@hidden>
 
        * mule.texi (File Name Coding): Document file-name encoding

=== modified file 'doc/emacs/killing.texi'
--- a/doc/emacs/killing.texi    2013-10-23 17:20:09 +0000
+++ b/doc/emacs/killing.texi    2013-12-17 15:57:38 +0000
@@ -417,13 +417,15 @@
 @kindex C-M-w
 @findex append-next-kill
   If a kill command is separated from the last kill command by other
-commands (not just numeric arguments), it starts a new entry on the kill
-ring.  But you can force it to append by first typing the command
address@hidden (@code{append-next-kill}) right before it.  The @kbd{C-M-w}
-tells the following command, if it is a kill command, to append the text
-it kills to the last killed text, instead of starting a new entry.  With
address@hidden, you can kill several separated pieces of text and
-accumulate them to be yanked back in one place.
+commands (not just numeric arguments), it starts a new entry on the
+kill ring.  But you can force it to combine with the last killed text,
+by typing @kbd{C-M-w} (@code{append-next-kill}) right beforehand.  The
address@hidden tells its following command, if it is a kill command, to
+treat the kill as part of the sequence of previous kills.  As usual,
+the kill is appended to the previous killed text if the command kills
+forward, and prepended if the command kills backward.  In this way,
+you can kill several separated pieces of text and accumulate them to
+be yanked back in one place.
 
   A kill command following @kbd{M-w} (@code{kill-ring-save}) does not
 append to the text that @kbd{M-w} copied into the kill ring.