From: "João Távora" <joaotavora@gmail.com>
To: 56696@debbugs.gnu.org
Subject: bug#56696: [PATCH] 29.0.50; compile.el doesn't always clean up after itself
Date: Fri, 22 Jul 2022 09:26:34 +0100 [thread overview]
Message-ID: <87ilnppn7p.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
Hello maintainers,
compile.el, which runs user code, doesn't use `unwind-protect` in its
process sentinel. I really think it should.
I noticed this while playing around with the excellent rmsbolt.el of Jay
Kamat, which makes use of compilation-finish-functions. If ones of
these functions errors, the user is stuck with a "[Compiling]" in her
modeline, even if compilation has long finished.
Let me know if there are any objections to this patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Clean-up-more-robustly-in-compile.el.patch --]
[-- Type: text/x-patch, Size: 2358 bytes --]
From de8025f19a7fe0cc37beeed61f4c1269de3519af Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jo=C3=A3o=20T=C3=A1vora?= <joaotavora@gmail.com>
Date: Fri, 22 Jul 2022 09:23:02 +0100
Subject: [PATCH] Clean up more robustly in compile.el
* lisp/progmodes/compile.el (compilation-sentinel): Use
unwind-protect.
---
lisp/progmodes/compile.el | 31 ++++++++++++++++---------------
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/lisp/progmodes/compile.el b/lisp/progmodes/compile.el
index c71a50d4fd..a665fccc73 100644
--- a/lisp/progmodes/compile.el
+++ b/lisp/progmodes/compile.el
@@ -2464,22 +2464,23 @@ compilation-handle-exit
(defun compilation-sentinel (proc msg)
"Sentinel for compilation buffers."
(if (memq (process-status proc) '(exit signal))
- (let ((buffer (process-buffer proc)))
- (if (null (buffer-name buffer))
- ;; buffer killed
- (set-process-buffer proc nil)
- (with-current-buffer buffer
- ;; Write something in the compilation buffer
- ;; and hack its mode line.
- (compilation-handle-exit (process-status proc)
- (process-exit-status proc)
- msg)
- ;; 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)))
+ (unwind-protect
+ (let ((buffer (process-buffer proc)))
+ (if (null (buffer-name buffer))
+ ;; buffer killed
+ (set-process-buffer proc nil)
+ (with-current-buffer buffer
+ ;; Write something in the compilation buffer
+ ;; and hack its mode line.
+ (compilation-handle-exit (process-status proc)
+ (process-exit-status proc)
+ msg))))
(setq compilation-in-progress (delq proc compilation-in-progress))
- (compilation--update-in-progress-mode-line))))
+ (compilation--update-in-progress-mode-line)
+ ;; 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))))
(defun compilation-filter (proc string)
"Process filter for compilation buffers.
--
2.37.0
[-- Attachment #3: Type: text/plain, Size: 9 bytes --]
João
next reply other threads:[~2022-07-22 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 8:26 João Távora [this message]
2022-07-23 5:57 ` bug#56696: [PATCH] 29.0.50; compile.el doesn't always clean up after itself Lars Ingebrigtsen
2022-07-23 9:25 ` João Távora
2022-07-25 13:20 ` João Távora
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilnppn7p.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=56696@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.