Re: mg: extract child status with WEXITSTATUS

On Tue, 09 Jan 2018 10:05:22 -0600, Scott Cheloha wrote: > After discussing it with jca@ and trying a few variations I've settled > on the attached diff. > > We indicate if sh(1) was signalled because we have that information at > hand. Otherwise we report the exit status as we always have.

Re: mg: extract child status with WEXITSTATUS

On Tue, Jan 09, 2018 at 10:05:22AM -0600, Scott Cheloha wrote: > After discussing it with jca@ and trying a few variations I've settled > on the attached diff. > > We indicate if sh(1) was signalled because we have that information at > hand. Otherwise we report the exit status as we always

Re: mg: extract child status with WEXITSTATUS

After discussing it with jca@ and trying a few variations I've settled on the attached diff. We indicate if sh(1) was signalled because we have that information at hand. Otherwise we report the exit status as we always have. ok? Index: grep.c

Re: mg: extract child status with WEXITSTATUS

On Tue, Jan 02 2018, Scott Cheloha wrote: > On Mon, Jan 01, 2018 at 09:07:25PM -0700, Todd C. Miller wrote: >> On Mon, 01 Jan 2018 19:54:07 -0600, Scott Cheloha wrote: >> >> > Hey, >> > >> > In the mg(1) *compile* buffer, currently you get incorrect >> > output like: >> >

Re: mg: extract child status with WEXITSTATUS

On Mon, Jan 01, 2018 at 09:07:25PM -0700, Todd C. Miller wrote: > On Mon, 01 Jan 2018 19:54:07 -0600, Scott Cheloha wrote: > > > Hey, > > > > In the mg(1) *compile* buffer, currently you get incorrect > > output like: > > > > Command exited abnormally with code 256 at [...] > > > > Using the

Re: mg: extract child status with WEXITSTATUS

On Mon, 01 Jan 2018 19:54:07 -0600, Scott Cheloha wrote: > Hey, > > In the mg(1) *compile* buffer, currently you get incorrect > output like: > > Command exited abnormally with code 256 at [...] > > Using the W* macros in corrects this: > > Command exited abnormally with code 1 at