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: Tue, 22 Sep 2015 14:51:58 +0100
Lines: 29
Approved: bug-bash@gnu.org
Message-ID: <mailman.1591.1442929931.19560.bug-bash@gnu.org>
References: <20150918151439.GA16455@chaz.gmail.com> <20150919203628.GA27872@chaz.gmail.com> <20150921094807.GA6229@chaz.gmail.com> <56005BC4.1070906@case.edu> <20150921212403.GB12000@chaz.gmail.com> <56015A8F.1040505@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1442929931 4212 208.118.235.17 (22 Sep 2015 13:52:11 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash <bug-bash@gnu.org>, Jilles Tjoelker <jilles@stack.nl>
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=aQ4WjtyJHT3rvYliY5IrgTdxyEDvcD0IWb1Sl+pwTko=; b=1ERYqTPJ5SpoUAMdB12Dk7U/zV7rkyLtzY/xR40bczHNPUl85P2zqBmJq8MAfX4uzN pD73Wxr1bUrk1RbZMnxdtVkSz9QXvkOt4vd4/qXGIa4oQ42NKMY01oob4YgtuDsejk22 q5qDHVwWTBURsaXeNv3NDXDNW4GbYYFR9di/z9wywFcv/6vosBzC5Rec6t9NDhyyFIP3 TjRR1MFUp7BpDuybIkLvu6Mj6rDFmlw7NXONx9hhKB1HJOXQNx/fiQo+YnX/+5h2CSxL lwWsBiJLt+F6HVhksbEm+C+SvLGDoAVqQkTGoIwab6BebfZYmOVov1W525yeCn4mO20C QiEA==
X-Received: by 10.180.107.1 with SMTP id gy1mr21357223wib.56.1442929919985; Tue, 22 Sep 2015 06:51:59 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <56015A8F.1040505@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::229
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:11537

2015-09-22 09:41:35 -0400, Chet Ramey:
[...]
> > AFAICT emacs starts a new process group (and makes it the
> > foreground process group).
> 
> Maybe, if it's being run from an interactive shell or in a separate
> X window.  On the other hand, run this script with `dash':
> 
> echo before
> emacs -nw /tmp/qux
> echo after
> 
> If you use ^G to abort an editing command in emacs, you won't see `after'
> displayed and the script will exit with status 130, even though emacs
> clearly doesn't die due to SIGINT.
[...]

It works for me (on Debian, displays both before and after) as
emacs starts in a new process group.

The problem seems to be with some ports of emacs to OS/X and was
already discussed at
http://www.zsh.org/mla/workers/2009/msg00926.html about the
MacPorts version of Emacs that doesn't seem to be starting the
new process group.

-- 
Stephane