Lars, your idea sounds pretty reasonable to me. In fact, you recently touched
the Ruby backend example checker in the manual.
commit f5b4bb4a6fa3adcb653cab5dc760745b896320bb
Author: Lars Ingebrigtsen <
larsi@gnus.org>
Date: Mon Oct 25 01:25:13 2021 +0200
Fix flymake example backend conditions in the manual
* doc/misc/flymake.texi (An annotated example backend): Also react
to `signal' process statuses (bug#51380).
diff --git a/doc/misc/flymake.texi b/doc/misc/flymake.texi
--- a/doc/misc/flymake.texi
+++ b/doc/misc/flymake.texi
@@ -777,1 +777,1 @@
- (when (eq 'exit (process-status proc))
+ (when (memq (process-status proc) '(exit signal))
The only question is why both I and you didn't venture to just use process-live-p
back then as you propose now. Because it seems to make sense. I personally
can't recall a reason other than my ignorance/oversight, but maybe you can?
João