branch: externals/el-job
commit 268102c786bf41f6f20e62cc69545e9b5c250b44
Author: Martin Edström <[email protected]>
Commit: Martin Edström <[email protected]>
Oops
---
el-job.el | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/el-job.el b/el-job.el
index 2c9664ee4b..33a1f3095d 100644
--- a/el-job.el
+++ b/el-job.el
@@ -668,10 +668,13 @@ same ID still has the benchmarks table and possibly
queued input."
(delete-process proc)
(and (= 0 el-job--debug-level)
;; Why can BUF be nil?
+ ;; And why is `kill-buffer' so unsafe?
+ ;; Can we upstream a `kill-buffer-safe' or `kill-buffer-assert'
+ ;; or `kill-live-buffer' that errors when argument is nil?
(buffer-live-p buf)
(kill-buffer buf))))
(and (= 0 el-job--debug-level)
- (buffer-live-p buf)
+ (buffer-live-p .stderr)
(kill-buffer .stderr))
(setf .busy nil)
(setf .ready nil)))
