aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar David Aspinall <da@inf.ed.ac.uk>2002-01-15 15:26:58 +0000
committerGravatar David Aspinall <da@inf.ed.ac.uk>2002-01-15 15:26:58 +0000
commita4cc4787ee2baf57d8f533a5942f231c2112ec38 (patch)
treeac66b3e0488ba87a07385ffc6a52914a2ba484d9
parent44880a9e0486db03afbb462d62ccee67daf8881f (diff)
Describe tracing improvements.
-rw-r--r--CHANGES26
1 files changed, 26 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 01c7a57c..58f64dfe 100644
--- a/CHANGES
+++ b/CHANGES
@@ -17,6 +17,31 @@
in font-lock, and its insiduous self-enabling actions.
Current status: broken in Emacs 20, working in 21.
+*** Support for "tracing" buffers improved and enabled by default.
+
+ (Support is enabled in Isabelle only so far)
+
+ Compared with experimental tracing in PG 3.3, there is now only one
+ tracing buffer, treated somewhat like a response buffer.
+
+ When large volumes of output arrive in Emacs, as typically is the
+ case during tracing (especially tracing looping tactics!), Emacs
+ may hog the CPU and spend all its time in the process filter
+ (especially with X symbol and fontification active). We call this
+ "choking".
+
+ If Emacs is choking, it may not process user events as swiftly as
+ normal and it can become difficult to interrupt the prover process
+ ordinarily (with the toolbar Stop button or C-c C-c). As a
+ workaround, PG will watch for keyboard quits when it's displaying
+ trace output, and send the prover an interrupt if it sees a quit
+ has been sent. So you should be able to interrupt with C-g during
+ choking.
+
+ If the choking effect slows down your prover too much by giving
+ Emacs too much CPU, disabling output fontification by customizing
+ `proof-output-fontify-enable' may help.
+
** Isabelle Changes
Isabelle/Isar syntax changes.
@@ -27,6 +52,7 @@
+
-----------------------------------------------------------------