From: Guido Berhoerster <gber@opensuse.org>
To: dash@vger.kernel.org
Subject: Re: exec command and error checking
Date: Wed, 29 Jan 2014 00:18:16 +0100 [thread overview]
Message-ID: <20140128231816.GC17217@hal.lan> (raw)
In-Reply-To: <20140128215916.GA59221@stack.nl>
* Jilles Tjoelker <jilles@stack.nl> [2014-01-28 23:06]:
> On Tue, Jan 28, 2014 at 02:17:59PM +0100, Guido Berhoerster wrote:
> > That's either a bug or an intended deviation from the POSIX
> > standard, you'll have to ask on the bug-bash list about that.
>
> The inconsistency appears to be in the behaviour on fatal errors in
> interactive shells. Strictly speaking, POSIX seems to require that the
bash actually exhibits this behavior as a non-interactive shell
and in POSIX mode as well.
--
Guido Berhoerster
next prev parent reply other threads:[~2014-01-28 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 12:16 exec command and error checking Марк Коренберг
2014-01-28 13:17 ` Guido Berhoerster
2014-01-28 15:32 ` Paul Gilmartin
2014-01-28 21:59 ` Jilles Tjoelker
2014-01-28 23:18 ` Guido Berhoerster [this message]
2014-01-29 3:19 ` Chet Ramey
2014-01-28 13:40 ` Seb
2014-01-28 14:05 ` Guido Berhoerster
2014-01-28 14:42 ` Seb
2014-01-28 14:52 ` Paul Gilmartin
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=20140128231816.GC17217@hal.lan \
--to=gber@opensuse.org \
--cc=dash@vger.kernel.org \
/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).