From 8b0645d63b6960e33dd4f258efb6488a7b2a1c89 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Tue, 6 Feb 2001 07:00:03 +0000 Subject: [PATCH] (Killing): Document that kill commands in a read-only buffer do put text into the kill ring, even if they don't kill it. --- man/killing.texi | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/man/killing.texi b/man/killing.texi index d790e78bae6..c297622188f 100644 --- a/man/killing.texi +++ b/man/killing.texi @@ -42,6 +42,11 @@ Setting the variable @code{kill-read-only-ok} to a non-@code{nil} value overrides that. To alert you to the fact that you killed read-only text, Emacs prints a message to that effect in the echo area. + When @code{kill-read-only-ok} is @code{nil}, Emacs beeps if you try to +kill text in a read-only buffers, but it puts the text you wanted to +kill into the kill ring anyway. This means you can use kill commands to +copy text from read-only buffers. + The delete commands include @kbd{C-d} (@code{delete-char}) and @key{DEL} (@code{delete-backward-char}), which delete only one character at a time, and those commands that delete only spaces or newlines. Commands -- 2.39.5