X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 18 Oct 2010 10:58:56 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Sending signals to a subprocess Message-ID: <20101018145856.GA14608@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4CB9DE15 DOT 8010308 AT cornell DOT edu> <4CB9E9C0 DOT 3000509 AT cornell DOT edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CB9E9C0.3000509@cornell.edu> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sat, Oct 16, 2010 at 02:06:56PM -0400, Ken Brown wrote: >On 10/16/2010 1:17 PM, Ken Brown wrote: >> I could use some help fixing a longstanding bug in the Cygwin build of >> emacs, in which emacs is unable to send signals to subprocesses. A >> symptom from the user's point of view is that one cannot interrupt a >> process in shell mode by typing C-c C-c. I've found a workaround that >> handles that case (SIGINT), as well as SIGQUIT and SIGTSTP. But as long >> as I'm fixing this, I'd like to do it right and figure out how to handle >> all signals. >> >> This boils down to finding the right process group ID to pass to 'kill'. >> On systems that have TIOCGPGRP, emacs uses the following code (in >> src/process.c) to get this ID: If it helps, I can implement TIOCGPGRP so it will be available in Cygwin 1.7.9. cgf -- 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