# HG changeset patch # User Richard M. Stallman # Date 726009674 0 # Node ID d1a56482a2af1095ac3749631610fd7cdf9806c6 # Parent f79966ac4f9d970e6147edc8619c286939bfc401 (compilation-sentinel): Change buffer-read-only with let. diff -r f79966ac4f9d -r d1a56482a2af lisp/progmodes/compile.el --- a/lisp/progmodes/compile.el Wed Dec 30 08:14:01 1992 +0000 +++ b/lisp/progmodes/compile.el Sat Jan 02 21:21:14 1993 +0000 @@ -367,26 +367,25 @@ ;; Write something in the compilation buffer ;; and hack its mode line. (set-buffer buffer) - (setq buffer-read-only nil) - (setq omax (point-max) - opoint (point)) - (goto-char omax) - ;; Record where we put the message, so we can ignore it - ;; later on. - (insert ?\n mode-name " " msg) - (forward-char -1) - (insert " at " (substring (current-time-string) 0 19)) - (forward-char 1) - (setq mode-line-process - (concat ": " - (symbol-name (process-status proc)))) - ;; Since the buffer and mode line will show that the - ;; process is dead, we can delete it now. Otherwise it - ;; will stay around until M-x list-processes. - (delete-process proc) - ;; Force mode line redisplay soon. - (set-buffer-modified-p (buffer-modified-p)) - (setq buffer-read-only t) ;I think is this wrong --roland + (let ((buffer-read-only nil)) + (setq omax (point-max) + opoint (point)) + (goto-char omax) + ;; Record where we put the message, so we can ignore it + ;; later on. + (insert ?\n mode-name " " msg) + (forward-char -1) + (insert " at " (substring (current-time-string) 0 19)) + (forward-char 1) + (setq mode-line-process + (concat ": " + (symbol-name (process-status proc)))) + ;; Since the buffer and mode line will show that the + ;; process is dead, we can delete it now. Otherwise it + ;; will stay around until M-x list-processes. + (delete-process proc) + ;; Force mode line redisplay soon. + (set-buffer-modified-p (buffer-modified-p))) (if (and opoint (< opoint omax)) (goto-char opoint)) (if compilation-finish-function