[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/man/killing.texi

From: Richard M. Stallman
Subject: [Emacs-diffs] Changes to emacs/man/killing.texi
Date: Wed, 26 Jun 2002 18:30:46 -0400

Index: emacs/man/killing.texi
diff -c emacs/man/killing.texi:1.26 emacs/man/killing.texi:1.27
*** emacs/man/killing.texi:1.26 Wed Sep 12 17:01:34 2001
--- emacs/man/killing.texi      Wed Jun 26 18:30:46 2002
*** 15,20 ****
--- 15,25 ----
  also be used for moving those units.  But there are other ways of
  copying text for special purposes.
+   On terminals that support multiple windows for multiple applications,
+ the kill commands also provide a way to select text for other applications
+ to copy, and the Emacs yank commands can access selections made by
+ other programs.
    Emacs has only one kill ring for all buffers, so you can kill text in
  one buffer and yank it in another buffer.
*** 54,59 ****
--- 59,69 ----
  individual descriptions use the words @samp{kill} and @samp{delete} to
  say which kind of operation they perform.
+   On window systems, the most recent kill done in Emacs is also the
+ primary selection, if it is more recent than any selection you made in
+ another program.  This means that the paste commands of other window
+ applications copy the text that you killed in Emacs.
  @cindex Delete Selection mode
  @cindex mode, Delete Selection
  @findex delete-selection-mode
*** 278,283 ****
--- 288,298 ----
  @item C-M-w
  Append next kill to last batch of killed text (@code{append-next-kill}).
  @end table
+   On window systems, if there is a current selection in some other
+ application, and you selected it more recently than you killed any
+ text in Emacs, @kbd{C-y} copies the selection instead of text
+ killed within Emacs.
  * Kill Ring::         Where killed text is stored.  Basic yanking.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]