From: Andreas Schwab <schwab@linux-m68k.org>
To: Max Kirillov <max@max630.net>
Cc: git@vger.kernel.org
Subject: Re: [question] && chaining vs shell loops
Date: Sun, 29 Mar 2015 18:07:39 +0200 [thread overview]
Message-ID: <874mp3948k.fsf@igel.home> (raw)
In-Reply-To: <20150329154840.GA8771@wheezy.local> (Max Kirillov's message of "Sun, 29 Mar 2015 18:48:41 +0300")
Max Kirillov <max@max630.net> writes:
> As far as I can see, loops in shell ignore non-zero exit
> codes of the bodies which are not last. For example, exit
> code of command 'for f in false true; do $f; done' is 0,
> even if there was false.
There is nothing special with loops, that's how the exit code of
compound commands is defined in general: it's the exit code of the last
executed command.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-03-29 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 15:48 [question] && chaining vs shell loops Max Kirillov
2015-03-29 16:07 ` Andreas Schwab [this message]
2015-03-29 17:43 ` Jeff King
2015-03-30 6:29 ` Max Kirillov
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=874mp3948k.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=max@max630.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.
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).