From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: But this one really is final
Date: Thu, 20 Mar 2003 23:59:18 -0600 [thread overview]
Message-ID: <uadfptg3t.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <u8yv9wsr1.fsf_-_@hschmi22.userfqdn.rz-online.de>
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
>>
>>> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>>>
>>>> The compilation buffer ends with
>>>> "Compilation exited abnormally with code 1 at Wed Mar 19 08:51:57"
>>>
>>> No idea about this one, however this is an Emacs message and I don't
>>> think we can blame newmake.bat for this. This one comes before the
>>> processing of info files, does it?
>>
>> No. This is the last line in the compilation buffer. Emacs is
>> reporting the process status returned by the external process just
>> executed (i.e. newmake). Emacs follows the Unix convention that a
>> zero status indicates normal completion while a non-zero status
>> indicates an error.
>
> Inspired by your post, I added error handling to newmake.bat (it checks
> for the returncodes of the programs it calls and if there are errors,
> it reports where they occurred and sets ERRORLEVEL to one, if there are
> no errors it sets ERRORLEVEL to 0.
>
> Here we go:
perfection.
Thanks,
Kevin
next prev parent reply other threads:[~2003-03-21 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 23:43 Final version of newmake.bat Frank Schmitt
2003-03-19 6:43 ` Kevin Greiner
2003-03-19 7:16 ` Frank Schmitt
2003-03-19 15:05 ` Kevin Greiner
2003-03-19 22:36 ` Frank Schmitt
2003-03-20 0:25 ` Kevin Greiner
2003-03-20 9:00 ` Frank Schmitt
2003-03-20 22:57 ` But this one really is final (was: Final version of newmake.bat) Frank Schmitt
2003-03-21 5:59 ` Kevin Greiner [this message]
2003-03-21 7:50 ` But this one really is final Frank Schmitt
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=uadfptg3t.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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.
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 NNTP newsgroup(s).