Processed: Re: Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2013-01-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #683671 [dash] dash doesn't ignore SIGINT when running a command that traps SIGINT, should implement WCE Severity set to 'important' from 'serious' -- 683671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683671 Debian Bug Tracking Sys

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2013-01-26 Thread Julien Cristau
Control: severity -1 important On Thu, Aug 2, 2012 at 11:03:11 -0700, Jonathan Nieder wrote: > severity 683671 serious I don't think this should be a blocker for release. Downgrading. Cheers, Julien signature.asc Description: Digital signature

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-28 Thread Vincent Lefevre
On 2012-08-28 11:05:45 +, Gerrit Pape wrote: > this bug log now suggests that zsh is in the same boat and the bug > possibly lies within emacs. Well, contrary to dash, zsh is not meant to be a POSIX shell, and cannot (must not) be used as /bin/sh (zsh has a sh emulation mode, but it is not per

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-28 Thread Gerrit Pape
On Thu, Aug 02, 2012 at 07:06:19PM +0200, Vincent Lefevre wrote: > Package: dash > Version: 0.5.7-3 > Severity: grave > Justification: causes non-serious data loss > > When running an interactive command, dash doesn't ignore SIGINT > and SIGQUIT. > > For instance, here's what I get with Emacs 24

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-08 Thread Jonathan Nieder
Vincent Lefevre wrote: > Ignoring SIGINT and SIGQUIT in the parent process prevents > coordination problems (two processes reading from the same terminal, > for example) when the executed command ignores or catches one of the > signals. > > and from the example implementation, one can see

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-07 Thread Vincent Lefevre
On 2012-08-07 08:26:46 -0700, Jonathan Nieder wrote: > Vincent Lefevre wrote: > > On 2012-08-02 11:03:11 -0700, Jonathan Nieder wrote: > > >> How about this patch (which at least gets rid of a mysterious code > >> artifact)? > > > > This is worse: Ctrl-G in emacs kills emacs! > > Weird. Why does

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-07 Thread Jonathan Nieder
Vincent Lefevre wrote: > On 2012-08-02 11:03:11 -0700, Jonathan Nieder wrote: >> How about this patch (which at least gets rid of a mysterious code >> artifact)? > > This is worse: Ctrl-G in emacs kills emacs! Weird. Why does system(3) claim it sets SIGINT to SIG_IGN, then? Puzzled, Jonathan

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-07 Thread Vincent Lefevre
Hi Jonathan, On 2012-08-02 11:03:11 -0700, Jonathan Nieder wrote: > Vincent Lefevre wrote: > > > Severity: grave > > Justification: causes non-serious data loss > > Can you explain that more precisely? At first glance it seems like an > ordinary important bug. Emacs is often called by other pr

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-02 Thread Jonathan Nieder
severity 683671 serious # not Debian-specific tags 683671 + upstream moreinfo quit Hi Vincent, Vincent Lefevre wrote: > Severity: grave > Justification: causes non-serious data loss Can you explain that more precisely? At first glance it seems like an ordinary important bug. [...] > [*] http:

Bug#683671: dash doesn't ignore SIGINT when running an interactive command

2012-08-02 Thread Vincent Lefevre
Package: dash Version: 0.5.7-3 Severity: grave Justification: causes non-serious data loss When running an interactive command, dash doesn't ignore SIGINT and SIGQUIT. For instance, here's what I get with Emacs 24 (not a previous version, since previously, Emacs had its own progress group, so tha