Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: SIGINT handling
Date: Thu, 24 Sep 2015 20:49:06 +0100
Lines: 58
Approved: bug-bash@gnu.org
Message-ID: <mailman.1757.1443124155.19560.bug-bash@gnu.org>
References: <20150918151439.GA16455@chaz.gmail.com> <55FDC8B4.4000505@case.edu> <20150919213101.GA4393@chaz.gmail.com> <56035164.30105@case.edu> <20150924060122.GA4338@chaz.gmail.com> <20150924062044.GA5756@chaz.gmail.com> <20150924135756.GA5007@chaz.gmail.com> <5604469C.4050406@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1443124155 2596 208.118.235.17 (24 Sep 2015 19:49:15 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash <bug-bash@gnu.org>
To: Chet Ramey <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=bmc0saUNc+CwS4AKTf0OqE0mZZgzU/y6zfU5l+XaWJ0=; b=AuGumg/kE9QhNyIJazN5QarNeACRV+Z2UFE5AFU0priCRTHdt/YCaoHq0HKE23XvXj TVlwyHtk90Xlj4jg22j0fzfmn29vK7fzIkFqT4CnyeitUwhTzz2BM2+QYwOpQfhScPkj h+GUhxJCHDlOFlwJqZO/0X4yQcYNOOGj55mbxiXe2cNNAW/KUgOlc5xGsrcRuF87JtYw 8V8vdQ+/wNlo21QjfO1jgSPW9CAQH+YBMOBDiXJQmRCz+cTQiQGKpmpDsgAp/+UOPIhl Pj6Ob3lCo2adGYU88wsgHnv1bK9q/ClEgfpqdHMmTGg5YpxQbKkqSvB7Ydw035Ba8A4f 5IVw==
X-Received: by 10.194.238.168 with SMTP id vl8mr1691041wjc.128.1443124148610; Thu, 24 Sep 2015 12:49:08 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <5604469C.4050406@case.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value).
X-Received-From: 2a00:1450:400c:c05::22d
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref: csiph.com gnu.bash.bug:11560

2015-09-24 14:53:16 -0400, Chet Ramey:
> On 9/24/15 9:57 AM, Stephane Chazelas wrote:
> 
> > IMO, the best approach would be to give up on WCE altogether
> > which is more source of frustration anyway than it has ever
> > helped. I live very well with a /bin/sh (dash) and interactive
> > shell (zsh) that don't do it.
> 
> We'll agree to disagree.
[...]


Now that we're settled on WCE,

would you agree that

a=$(cmd-that-catches-sigint)

should behave like

(cmd-that-catches-sigint)

(as in, not exit the shell as per WCE)?

What about $PIPESTATUS?

In:

cmd-that-catches-sigint | cmd-that-does-not
or
cmd-that-does-not | cmd-that-catches-sigint

Should we exit on SIGINT or leave that command run in
background?

Should pipefail have an influence on the behaviour? What about
lastpipe?

What about when using the wait builtin?

Why should:

cmd & wait "$!"

be treated differently from

cmd

?

Because cmd's stdin is /dev/null and so is unlikely to be an
interactive command?

So we admit WCE is a kludge 

-- 
Stephane