# HG changeset patch
# User Luc Teirlinck <teirllm@auburn.edu>
# Date 1083450279 0
# Node ID 56bb135eddf9e2b26788f71861602ca9a35731d0
# Parent  c2bea9cc10a350b058325f44b3d21e84a9d32656
*** empty log message ***

diff -r c2bea9cc10a3 -r 56bb135eddf9 etc/NEWS
--- a/etc/NEWS	Sat May 01 21:19:31 2004 +0000
+++ b/etc/NEWS	Sat May 01 22:24:39 2004 +0000
@@ -91,8 +91,22 @@
 * Changes in Emacs 21.4
 
 ---
-** The IELM prompt is now, by default, read-only.  This can be
-controlled with the new user option `ielm-prompt-read-only'.
+** The comint prompt can now be made read-only, using the new user
+option `comint-prompt-read-only'.  This is not enabled by default,
+except in IELM buffers.  The read-only status of IELM prompts can be
+controlled with the new user option `ielm-prompt-read-only', which
+overrides `comint-prompt-read-only'.  The new commands
+`comint-kill-whole-line' and `comint-kill-region' support editing
+comint buffers with read-only prompts.  `comint-kill-whole-line' is
+like `kill-whole-line', but ignores both read-only and field
+properties.  Hence, it will always kill entire lines, including any
+prompts.  `comint-kill-region' is like `kill-region', except that it
+ignores read-only properties, if it is safe to do so.  This means that
+if any part of a prompt is deleted, then the entire prompt must be
+deleted and that all prompts must stay at the beginning of a line.  If
+this is not the case, then `comint-kill-region' behaves just like
+`kill-region' if read-only are involved: it copies the text to the
+kill-ring, but does not delete it.
 
 ** You can now use next-error (C-x `) and previous-error to advance to
 the next/previous matching line found by M-x occur.