From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6430@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#6430: Emacs WINDOWS truncates exit status of processes to 8 bits
Date: Thu, 16 Jun 2016 06:13:46 +0200 [thread overview]
Message-ID: <87wplpixdx.fsf@wanadoo.es> (raw)
In-Reply-To: <83mvmldfnp.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Jun 2016 05:35:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> We only solve real-life problems in Emacs, not academical ones. Life
> is too hard for anything else.
The MS toolchain (to name just a case that we could expect to be used
from Emacs) outputs quite a few exit codes larger than 255. If the user
is interested on detecting one of those codes, he will be out of luck.
The fact that there is just one bug report about this limitation of
Emacs possibly shows that users are only interested on differentiating
success from failure, zero from non-zero exit codes.
next prev parent reply other threads:[~2016-06-16 4:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 17:20 bug#6430: Emacs WINDOWS truncates exit status of processes to 8 bits macross84
2016-06-14 2:48 ` Noam Postavsky
2016-06-14 13:07 ` Óscar Fuentes
2016-06-14 14:35 ` Eli Zaretskii
2016-06-14 21:48 ` Noam Postavsky
2016-06-15 2:39 ` Eli Zaretskii
2016-06-15 12:30 ` Óscar Fuentes
2016-06-15 15:02 ` Eli Zaretskii
2016-06-15 15:15 ` Óscar Fuentes
2016-06-15 15:40 ` Eli Zaretskii
2016-06-15 17:14 ` Óscar Fuentes
2016-06-15 17:32 ` Eli Zaretskii
2016-06-15 17:36 ` Óscar Fuentes
2016-06-15 18:04 ` Eli Zaretskii
2016-06-15 18:22 ` Óscar Fuentes
2016-06-15 18:50 ` Eli Zaretskii
2016-06-15 19:32 ` Óscar Fuentes
2016-06-16 2:35 ` Eli Zaretskii
2016-06-16 4:13 ` Óscar Fuentes [this message]
2016-06-16 15:07 ` Eli Zaretskii
2016-06-16 17:56 ` Óscar Fuentes
2016-06-16 19:05 ` Eli Zaretskii
2020-11-19 4:05 ` Stefan Kangas
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=87wplpixdx.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=6430@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.