Subject: bug#41099: 28.0.50; TRAMP process-file ignores exit status of remote process

From: Michael Albinus <[email-masked]>
Date: Sun, 17 May 2020 10:19:26 +0200

Dmitry Gutov <[email-masked]> writes:

Hi Dmitry,

> OK, so if I understand you right, Tramp ends up doing some extra
> computations to get that info, and that makes it slower. I suppose
> this could be a reason to make the "correct" behavior disabled by
> default.

That's not the problem. Tramp cannot determine reliably, whether a
remote process has been interrupted by a signal. It uses a heuristic
(all exit codes greater than 128), but Noam has shown that this is not
bullet-proof. See the discussion in this bug.

Best regards, Michael.