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