Avoid name conflicts with outline.el. Use 3 installments to keep

[gnu-emacs] / man / killing.texi

diff --git a/man/killing.texi b/man/killing.texi
index 0811f1f1f38f117a535e80f7fccd2d944de53e38..4dbcc2e6a10abf3d7daf6b8a3a6026a5aa25c385 100644 (file)
--- a/man/killing.texi
+++ b/man/killing.texi
@@ -15,6 +15,11 @@ is versatile, because the many commands for killing syntactic units can
 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,6 +59,11 @@ data generally do a kill operation instead.  The commands' names and
 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
@@ -211,7 +221,6 @@ following newline.  This variable is normally @code{nil}.
 @findex kill-region
 @kindex C-w
 
-@c DoubleWideCommands
 @table @kbd
 @item C-w
 Kill region (from point to the mark) (@code{kill-region}).
@@ -280,6 +289,11 @@ Save region as last killed text without actually killing it
 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.
+
 @menu
 * Kill Ring::          Where killed text is stored.  Basic yanking.
 * Appending Kills::    Several kills in a row all yank together.
@@ -306,6 +320,15 @@ mark after it.  This happens only if the argument is specified with just
 a @kbd{C-u}, precisely.  Any other sort of argument, including @kbd{C-u}
 and digits, specifies an earlier kill to yank (@pxref{Earlier Kills}).
 
+@cindex yanking and text properties
+@vindex yank-excluded-properties
+  The yank commands discard certain text properties from the text that
+is yanked, those that might lead to annoying results.  For instance,
+they discard text properties that respond to the mouse or specify key
+bindings.  The variable @code{yank-excluded-properties} specifies the
+properties to discard.  Yanking of register contents and rectangles
+also discard these properties.
+
 @kindex M-w
 @findex kill-ring-save
   To copy a block of text, you can use @kbd{M-w}