From: Michael Albinus <michael.albinus@gmx.de>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 41099@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#41099: 28.0.50; TRAMP process-file ignores exit status of remote process
Date: Sat, 23 May 2020 21:35:42 +0200 [thread overview]
Message-ID: <87tv06phpt.fsf@gmx.de> (raw)
In-Reply-To: <CAArVCkTf7kT9i75YxayGJvYuhfQ465FwCkpf3XZWo=2ZH2QScw@mail.gmail.com> (Philipp Stephani's message of "Sat, 23 May 2020 21:17:44 +0200")
Philipp Stephani <p.stephani2@gmail.com> writes:
Hi Philipp,
> To be fair, I care far more about the initial bug report (correct
> treatment of exit codes below 128). Many programs follow the
> convention to treat small nonzero exit codes as "expected" errors
> (e.g. grep: 1 means no match found) and higher exit codes as
> "unexpected" errors. In that light a distinction between small exit
> codes is more important than trying to achieve 100% correctness when
> it comes to signals. So I'm definitely fine with adding a
> customization option: anything better would likely be more complex
> than is warranted.
Thanks for the feedback. Since the user option has been added already, I
believe we could regard this bug as solved entirely.
Best regards, Michael.
next prev parent reply other threads:[~2020-05-23 19:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 18:49 bug#41099: 28.0.50; TRAMP process-file ignores exit status of remote process Philipp Stephani
2020-05-05 19:02 ` Philipp Stephani
2020-05-05 19:25 ` Michael Albinus
2020-05-06 8:38 ` Michael Albinus
2020-05-06 10:38 ` Philipp Stephani
2020-05-06 10:50 ` Philipp Stephani
2020-05-06 11:24 ` Michael Albinus
2020-05-06 13:32 ` Michael Albinus
2020-05-06 15:36 ` Philipp Stephani
2020-05-06 17:30 ` Michael Albinus
2020-05-06 17:56 ` Philipp Stephani
2020-05-06 17:57 ` Philipp Stephani
2020-05-06 19:33 ` Michael Albinus
2020-05-07 8:29 ` Michael Albinus
2020-05-09 19:53 ` Philipp Stephani
2020-05-14 1:39 ` Noam Postavsky
2020-05-14 11:00 ` Michael Albinus
2020-05-14 12:38 ` Philipp Stephani
2020-05-14 12:50 ` Andreas Schwab
2020-05-14 14:07 ` Noam Postavsky
2020-05-14 14:48 ` Philipp Stephani
2020-05-14 15:49 ` Michael Albinus
2020-05-16 12:06 ` Michael Albinus
2020-05-16 12:11 ` Dmitry Gutov
2020-05-16 12:19 ` Michael Albinus
2020-05-16 22:03 ` Dmitry Gutov
2020-05-17 8:19 ` Michael Albinus
2020-05-23 19:17 ` Philipp Stephani
2020-05-23 19:35 ` Michael Albinus [this message]
2020-05-23 19:42 ` Philipp Stephani
2020-05-06 17:41 ` Andreas Schwab
2020-05-06 17:53 ` Philipp Stephani
2020-05-06 18:58 ` Andreas Schwab
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv06phpt.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=41099@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=npostavs@gmail.com \
--cc=p.stephani2@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).