diff options
| author | Chong Yidong | 2013-12-17 23:57:38 +0800 |
|---|---|---|
| committer | Chong Yidong | 2013-12-17 23:57:38 +0800 |
| commit | 9718dea2e16ce975d2cda02985ed2349f2d7a085 (patch) | |
| tree | 717ef8c1ca83ce88376ca4ef3fc56dfffe03c18f | |
| parent | 76da345537e550892b8bc9434ee0b3b82b44c573 (diff) | |
| download | emacs-9718dea2e16ce975d2cda02985ed2349f2d7a085.tar.gz emacs-9718dea2e16ce975d2cda02985ed2349f2d7a085.zip | |
* killing.texi (Appending Kills): Note that append-next-kill can prepend the kill.
| -rw-r--r-- | doc/emacs/ChangeLog | 5 | ||||
| -rw-r--r-- | doc/emacs/killing.texi | 16 |
2 files changed, 14 insertions, 7 deletions
diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog index c765d479385..c5330da779b 100644 --- a/doc/emacs/ChangeLog +++ b/doc/emacs/ChangeLog | |||
| @@ -1,3 +1,8 @@ | |||
| 1 | 2013-12-17 Chong Yidong <cyd@gnu.org> | ||
| 2 | |||
| 3 | * killing.texi (Appending Kills): Note that append-next-kill can | ||
| 4 | prepend the kill. | ||
| 5 | |||
| 1 | 2013-12-12 Eli Zaretskii <eliz@gnu.org> | 6 | 2013-12-12 Eli Zaretskii <eliz@gnu.org> |
| 2 | 7 | ||
| 3 | * mule.texi (File Name Coding): Document file-name encoding | 8 | * mule.texi (File Name Coding): Document file-name encoding |
diff --git a/doc/emacs/killing.texi b/doc/emacs/killing.texi index 30b3a2c5ff0..5f2b5aa6605 100644 --- a/doc/emacs/killing.texi +++ b/doc/emacs/killing.texi | |||
| @@ -417,13 +417,15 @@ killed it. | |||
| 417 | @kindex C-M-w | 417 | @kindex C-M-w |
| 418 | @findex append-next-kill | 418 | @findex append-next-kill |
| 419 | If a kill command is separated from the last kill command by other | 419 | If a kill command is separated from the last kill command by other |
| 420 | commands (not just numeric arguments), it starts a new entry on the kill | 420 | commands (not just numeric arguments), it starts a new entry on the |
| 421 | ring. But you can force it to append by first typing the command | 421 | kill ring. But you can force it to combine with the last killed text, |
| 422 | @kbd{C-M-w} (@code{append-next-kill}) right before it. The @kbd{C-M-w} | 422 | by typing @kbd{C-M-w} (@code{append-next-kill}) right beforehand. The |
| 423 | tells the following command, if it is a kill command, to append the text | 423 | @kbd{C-M-w} tells its following command, if it is a kill command, to |
| 424 | it kills to the last killed text, instead of starting a new entry. With | 424 | treat the kill as part of the sequence of previous kills. As usual, |
| 425 | @kbd{C-M-w}, you can kill several separated pieces of text and | 425 | the kill is appended to the previous killed text if the command kills |
| 426 | accumulate them to be yanked back in one place. | 426 | forward, and prepended if the command kills backward. In this way, |
| 427 | you can kill several separated pieces of text and accumulate them to | ||
| 428 | be yanked back in one place. | ||
| 427 | 429 | ||
| 428 | A kill command following @kbd{M-w} (@code{kill-ring-save}) does not | 430 | A kill command following @kbd{M-w} (@code{kill-ring-save}) does not |
| 429 | append to the text that @kbd{M-w} copied into the kill ring. | 431 | append to the text that @kbd{M-w} copied into the kill ring. |