From 644ecad64469227e8a84673d26c188c5553c2562 Mon Sep 17 00:00:00 2001
From: David Aspinall
Date: Sun, 19 Mar 2000 06:51:04 +0000
Subject: Updated.

---
 BUGS | 20 ++++++++++++++------
 1 file changed, 14 insertions(+), 6 deletions(-)

(limited to 'BUGS')

diff --git a/BUGS b/BUGS
index 5ff3c5ed..a1a9f783 100644
--- a/BUGS
+++ b/BUGS
@@ -63,21 +63,29 @@ simplifier, when tracing rewriting.
  disabled/enabled when they shouldn't be.  An extra click on the
  toolbar solves this.
 
-** Ordinary undo in the script buffer can edit the "uneditable region"
+** Strict read only disabled by default in FSF Emacs.
 
-  In XEmacs.  This doesn't happen in FSFmacs.  Test case:
-  Insert some nonsense text after the locked region.
-  Kill the line. Process to the next command.
-  Press C-x u, nonsense text appears in locked region.
-  Workaround: take care with undo in XEmacs.
+  Unfortunately strict read only is incompatible with font lock in
+  FSF Emacs, so it is disabled by default.  Instead, you get a warning message
+  if the locked region is edited.
 
 ** In FSFmacs, spurious "Region read only" errors
 
+ Same problem as above, different symptom.
  When proof-strict-read-only is set and font lock is on, these
  errors are given which break font lock.   
  Workaround: turn off proof-strict-read-only, font-lock, or for
  the best of all possible worlds, switch to XEmacs.
 
+
+** Emacs undo in the script buffer can edit the "uneditable region"
+
+  In XEmacs.  This doesn't happen in FSFmacs.  Test case:
+  Insert some nonsense text after the locked region.
+  Kill the line. Process to the next command.
+  Press C-x u, nonsense text appears in locked region.
+  Workaround: take care with undo in XEmacs.
+
 ** As of FSFmacs 20.3, multi-byte character codes are used.  
 
   This breaks some of the code in Proof General, which is turned off in
-- 
cgit v1.2.3