From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: macross84@ozu.es, 6430@debbugs.gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#6430: Emacs WINDOWS truncates exit status of processes to 8 bits
Date: Wed, 15 Jun 2016 14:30:20 +0200 [thread overview]
Message-ID: <87mvmmk52b.fsf@wanadoo.es> (raw)
In-Reply-To: <83d1njdvk9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Jun 2016 05:39:50 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Not really sure what this reformatting is about, but I think the point
>> is that the original value does not return to lisp.
>
> Why is that a problem?
Because Emacs is reporting something false?
> The important information that I thought this was about is in the
> upper 4 bits of the status, and it doesn't get lost -- it's passed
> back to Emacs as the signal (if any) that caused the subprocess to
> exit.
>
> If there are any important use cases with programs that return status
> above 255, we can easily change the definition of WEXITSTATUS for
> Windows. But I have yet to see a real-life example of such a program,
> or any complaint about the current WEXITSTATUS definition in Emacs.
You are fortunate enough to live in a world of applications ported from
*nix :-) (and so do I, for the most part.)
When a Windows application calls an API that fails and the application
has no method for recovering from the error, it is customary to exit
with the error code of the API (usually obtained with GetLastError).
next prev parent reply other threads:[~2016-06-15 12:30 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 [this message]
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
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=87mvmmk52b.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=6430@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=macross84@ozu.es \
--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.