X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20100915153611.GC2124@ednor.casa.cgf.cx> References: <4C8FB7B6 DOT 1030300 AT gmail DOT com> <4C90E6C4 DOT 9050503 AT gmail DOT com> <20100915153611 DOT GC2124 AT ednor DOT casa DOT cgf DOT cx> Date: Mon, 20 Sep 2010 12:22:33 +0200 Message-ID: Subject: Re: ssh from linux to cygwin + CUI + Ctrl-C From: "Ilia K." To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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 It looks like my reply got lost in mailer's spam filters, reposting. On Wed, Sep 15, 2010 at 5:36 PM, Christopher Faylor wrote: ... > Cygwin summarily halts a pure-Windows process on receiving a CTRL-C. > There is no way around that other than to relink the program to use > Cygwin. Do you state that there is absolutely no way to make it work as I need? This would be very pity... Do you know what's the difference between running bash from sshd and from the desktop? In the later case, Ctrl-C works as expected! To me it looks like cygwin knows how to pass Ctrl-C to native apps, but sshd somehow interferes with it. Regards, Ilia. -- 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