Re: SIGINT handling

From	Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: SIGINT handling
Date	2015-09-22 14:51 +0100
Message-ID	<mailman.1591.1442929931.19560.bug-bash@gnu.org> (permalink)
References	(1 earlier) <20150919203628.GA27872@chaz.gmail.com> <20150921094807.GA6229@chaz.gmail.com> <56005BC4.1070906@case.edu> <20150921212403.GB12000@chaz.gmail.com> <56015A8F.1040505@case.edu>

Show all headers | View raw

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

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: SIGINT handling Stephane Chazelas <stephane.chazelas@gmail.com> - 2015-09-22 14:51 +0100

csiph-web