diff options
| author | David Aspinall | 2000-03-19 06:51:04 +0000 |
|---|---|---|
| committer | David Aspinall | 2000-03-19 06:51:04 +0000 |
| commit | 644ecad64469227e8a84673d26c188c5553c2562 (patch) | |
| tree | 346e823a71c04717ef99619ce4c499665d7a9875 | |
| parent | 5065206902370d4e0e35096967f40f07b2bc1d18 (diff) | |
Updated.
| -rw-r--r-- | BUGS | 20 |
1 files changed, 14 insertions, 6 deletions
@@ -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 |
