# HG changeset patch
# User Luc Teirlinck <teirllm@auburn.edu>
# Date 1094178971 0
# Node ID 36c1c98acd4b73d188f6f60027f5e362938c427d
# Parent  621733a9d27b67dd8c1afbe509d74469d680a2bc
(Killing): Correct description of kill commands in read-only buffer.

diff -r 621733a9d27b -r 36c1c98acd4b man/killing.texi
--- a/man/killing.texi	Thu Sep 02 23:26:16 2004 +0000
+++ b/man/killing.texi	Fri Sep 03 02:36:11 2004 +0000
@@ -1,5 +1,6 @@
 @c This is part of the Emacs manual.
-@c Copyright (C) 1985,86,87,93,94,95,97,00,2001 Free Software Foundation, Inc.
+@c Copyright (C) 1985,86,87,93,94,95,97,2000,2001,2004
+@c   Free Software Foundation, Inc.
 @c See file emacs.texi for copying conditions.
 @iftex
 @chapter Killing and Moving Text
@@ -49,11 +50,12 @@
   You cannot kill read-only text, since such text does not allow any
 kind of modification.  But some users like to use the kill commands to
 copy read-only text into the kill ring, without actually changing it.
-If you set the variable @code{kill-read-only-ok} to a non-@code{nil}
-value, the kill commands work specially in a read-only buffer: they
-move over text, and copy it to the kill ring, without actually
-deleting it from the buffer.  When this happens, a message in the echo
-area tells you what is happening.
+Therefore, the kill commands work specially in a read-only buffer:
+they move over text, and copy it to the kill ring, without actually
+deleting it from the buffer.  Normally, Emacs beeps and prints an
+error message when this happens.  But if you set the variable
+@code{kill-read-only-ok} to a non-@code{nil} value, it just prints a
+message in the echo area, telling you what is happening.
 
   The delete commands include @kbd{C-d} (@code{delete-char}) and
 @key{DEL} (@code{delete-backward-char}), which delete only one