aboutsummaryrefslogtreecommitdiffhomepage
path: root/generic
diff options
context:
space:
mode:
authorGravatar David Aspinall <da@inf.ed.ac.uk>2009-05-25 22:23:47 +0000
committerGravatar David Aspinall <da@inf.ed.ac.uk>2009-05-25 22:23:47 +0000
commitcafa86e49837c6cd526b9bb932a76d1dc3554a52 (patch)
tree8dd9c191765b28643c65011bb95b17b3ebad4c15 /generic
parent412261d34570dfe9af53e492fd68341ef24e2e98 (diff)
Set default value for `buffer-invisibility-spec'
Diffstat (limited to 'generic')
-rw-r--r--generic/proof-script.el15
1 files changed, 8 insertions, 7 deletions
diff --git a/generic/proof-script.el b/generic/proof-script.el
index 38626c5e..b7be033e 100644
--- a/generic/proof-script.el
+++ b/generic/proof-script.el
@@ -2467,13 +2467,11 @@ command."
(make-local-variable 'indent-line-function)
(setq indent-line-function 'proof-indent-line)
- ;; During write-file it can happen that we re-set the mode for
- ;; the currently active scripting buffer. The user might also
- ;; do this for some reason. We could maybe let
- ;; this pass through, but it seems safest to treat it as
- ;; a kill buffer operation (retract and clear spans).
- ;; (NB: other situations seem to cause double successive calls to
- ;; proof-mode).
+ ;; During write-file it can happen that we re-set the mode for the
+ ;; currently active scripting buffer. The user might also do this
+ ;; for some reason. We could maybe let this pass through, but it
+ ;; seems safest to treat it as a kill buffer operation (retract and
+ ;; clear spans). NB: other situations cause double calls to proof-mode.
(if (eq (current-buffer) proof-script-buffer)
(proof-script-kill-buffer-fn))
@@ -2481,6 +2479,9 @@ command."
;; that they can be adjusted by prover specific code if need be.
(proof-script-set-buffer-hooks)
+ ;; We use a list to manage invisibility of buffer parts
+ (setq buffer-invisibility-spec nil)
+
(add-hook 'after-set-visited-file-name-hooks
'proof-script-set-visited-file-name nil t)