This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ctrl-c not working during bash command line editing

On Mar  2 12:10, Corinna Vinschen wrote:
> On Mar  2 11:18, Corinna Vinschen wrote:
> > On Mar  1 19:22, Kitchens wrote:
> > > I've noticed this as well, and it seems to be a difference between
> > > /dev/consX and /dev/ptyX ttys. Mintty seems to work fine, whereas
> > > cmd.exe or Console2 (basically a cmd wrapper) cannot CTRL+C on the
> > > command line to abort it. Ctrl+C does, however, issue a SIGINT for a
> > > running process.
> > 
> > Confirmed.  If you start an interactive subshell, Ctrl-C starts working
> > again in there, so this only affects the parent process in a console.
> > 
> > I think I see where this is coming from.  I applied a patch to CVS which
> > fixes this issue, at least for applications calling tcsetattr, like
> > interactive processes usually do.  AFAICS, there's another patch required
> > for non-interactive processes.
> No, that was based on a wrong assumption, apparently.  All apps I started
> could be stopped w/ Ctrl-C now.

I juct created a developer snapshot for testing.  Please give it a try:


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]