On Fri, Aug 3, 2012 at 9:51 AM, marco atzeri wrote: > On 8/3/2012 3:43 PM, Earnie Boyd wrote: >> >> On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote: >>> >>> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote: >>>> >>>> Steps to reproduce: >>>> >>>> 1. Start cygwin using cygwin.bat >>>> 2. Run `ping -t google.com` >>>> 3. Try breaking it with Ctrl+C >>>> >>>> Expected behaviur: >>>> The ping breaks execution and the command prompt is shown and available >>>> >>>> Actual behaviour: >>>> Nothing happens, ping loops until killed with `/usr/bin/kill -f PID` >>> >>> >>> I don't have a "cygwin.bat" but if I start bash via Start->Run this >>> works for me. ping is interrupted by CTRL-C. >>> >> >> If executed from mintty CTRL-C works to interrupt the process. If >> executed from a Windows console terminal (and I don't mean cmd.exe) > > > a "windows console terminal" is cmd.exe, IMHO. > There are no other console in windows as standard installation. >
A console terminal is used for any process needing stdin/stdout/stderr, that isn't just cmd.exe. >> ping doesn't interrupt with CTRL-C. Another interesting thing, ``run >> bash --login -i'' starts the process but the Window closes with the >> process in the background and I have to use the Task Manager to kill >> it, Cygwin's kill doesn't kill it. However ``run mintty'' works >> regardless. > > > have you checked the manual ? > > RUN(1) run 1.1.13 RUN(1) > > NAME > run - start programs with hidden console window Ok, sorry, I assumed it was similar to cmd /c start. But I should be able to kill it with Cygwin's kill command. Also the doing ``run bash --login -i'' the terminal command prompt doesn't return to the issuing job either. -- Earnie -- https://sites.google.com/site/earnieboyd -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
