aboutsummaryrefslogtreecommitdiffhomepage
path: root/BUGS
diff options
context:
space:
mode:
authorGravatar David Aspinall <da@inf.ed.ac.uk>1999-11-17 13:52:23 +0000
committerGravatar David Aspinall <da@inf.ed.ac.uk>1999-11-17 13:52:23 +0000
commitfc16609ad30f905123630f95af77d7212f41557c (patch)
tree36dd54c38bb40c50b9c7f48eb1ad615e24f4913c /BUGS
parentbf6e48f675748f891a59cb71da59c5113ccc2ac6 (diff)
Updated
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS16
1 files changed, 11 insertions, 5 deletions
diff --git a/BUGS b/BUGS
index 71bea29d..b9fe6a6b 100644
--- a/BUGS
+++ b/BUGS
@@ -16,6 +16,10 @@ mess. The underlying text property implementation has changed
and it seems difficult to get the desired behaviour of highlighting
now. Workaround: switch to using XEmacs.
+* If you use C-x C-v or C-x C-w on a script file which is in active
+scripting mode, Proof General will lose track of the file.
+Workaround: always turn off active scripting first with C-c C-s.
+
* Toolbar enablers for XEmacs 21: since these have been switched on,
it is apparent that the recognition of completed proofs may be
unreliable (it wasn't used before). Also there is a timing issue,
@@ -89,6 +93,8 @@ using rsh instead, it is said to forward signals to the remote command.
LEGO Proof General Bugs
=======================
+* PBP doesn't work on FSF, see note above.
+
* [FSF specific] `proof-zap-commas-region' does not work for Emacs
20.2 on lego/example.l . On *initially* fontifying the buffer,
commas are not zapped [unfontified]. However, when entering text,
@@ -99,11 +105,11 @@ LEGO Proof General Bugs
Proof General and gets stuck. Workaround: Directly enter "Configure
AnnotateOn" in the Proof Shell to recover.
-* After a `Discharge', retraction ought to only be possible back to the
-first declaration/definition which is discharged. However, LEGO Proof
-General does not know that Discharge has such a non-local effect.
-Workaround: retract back to the first declaration/definition which is
-discharged.
+* After a `Discharge', retraction ought to only be possible back to
+the first declaration/definition which is discharged. However, LEGO
+Proof General does not know that Discharge has such a non-local
+effect. Workaround: retract back to the first
+declaration/definition which is discharged.
* A thorny issue is local definitions in a proof state. LEGO cannot
undo them explicitly. Workaround: retract back to a command before a