[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: tcsh's exit codes
From:       rank1seeker () gmail ! com
Date:       2012-06-25 14:02:56
Message-ID: 20120625.140256.620.1 () DOMY-PC
[Download RAW message or body]

----- Original Message -----
From: Johan van Selst <johans@stack.nl>
To: rank1seeker@gmail.com
Cc: hackers@freebsd.org
Date: Sat, 23 Jun 2012 19:14:07 +0200
Subject: Re: tcsh's exit codes

> rank1seeker@gmail.com wrote:
> > There is something wrong with tcsh shell:
> > 
> > # mergemaster -V | grep '\--run-updates'
> >     Returned exit code 1
> > # mergemaster -V | grep -q '\--run-updates'
> >     Returned exit code 141
> 
> I believe this has been a feature of csh and tcsh since the dark ages.
> Negative status codes propagate through pipelines (and through backtick
> sub-commands as well). In fact the returned $status value is the value
> of the last command that returned an error (non-zero) status code.
> This makes it easy to determine if a pipeline command sequence has
> failed.
> 
> The 141 status code indicates a sigpipe: the pipeline was not completely
> read (as described in the grep manual for this case). This also is the
> common exit code when using head(1) for example.
> 
> This error-propagation behaviour can be suppessed with 'unset anyerror'
> in tcsh. In that case it should work as you expect. But note that your
> commands are no longer compatible with 'good old' csh behaviour then.
> 
> 
> Regards,
> Johan


Thanks for clarification J.

D.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]