X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <32d701820709071142u31898d8aq15a5f5baedbf0114@mail.gmail.com> Date: Fri, 7 Sep 2007 11:42:43 -0700 From: "Alex Worden" To: cygwin AT cygwin DOT com Subject: Ctrl-C will not kill a process started from cygwin shell MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, I'm sorry if this is an obvious question but I searched and couldn't find an obvious answer and wasn't sure what to search for... It seems that some processes I start from a cygwin shell start in the foreground - whereas if I start them from a cmd shell they start in the background. (I know I can append an & but that's not the point here). One process I know of in particular is my favoured Micro Emacs editor (available at http://www.jasspa.com/). When this starts in the foreground from cygwin, even Ctrl-C will not kill the process. What determines this behavior and can I do anything about it. I ask because more importantly, I am running into issues running Maven tasks that do not return to the shell after completion. The only option available to be is to kill the entire cygwin shell. Please can someone explain what might be happening here, or point me at documentation on this subject. Thanks! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/