Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <8F23E55D511AD5119A6800D0B76FDDE11E100D@cpex3.channelpoint.com> From: Troy Noble To: "'cygwin AT cygwin DOT com'" Subject: RE: Brainstorming a fix for CTRL-C handling in an emacs shell buf fer (non-TTY) Date: Sat, 5 May 2001 10:36:18 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/) Christopher, I tried the latest winsup sources out of CVS this morning (ran cvs checkout at approx 5/5/2000 8:35AM MDT) I am still seeing the CTRL-C problem when running bash or ash inside emacs shell buffer. The patch I sent yesterday does fix it even in this latest code. http://sources.redhat.com/ml/cygwin/2001-05/msg00261.html So would you entertain adding the new CYGWIN= option? If you need me to diff and re-send the patch against the latest CVS winsup sources, I'd be glad to do so... and if so, let me know if you preferred: 1. the one that used the environment variable. This is my personal favorite since it won't affect all cygwin processes that share the DLL, just those in which a user had defined the appropriate environment variable. So one could run a bash inside emacs and a bash in a console window or an rxvt, and the two could behave differently. Then a user could do something like this for example in their .bashrc: if [ X"${EMACS}" != X ]; then export CYGWIN_HANDLE_NONTTY_CTRL_C=1 fi 2. OR the one that adds the CYGWIN=enable_nontty_ctrl_c option. Thanks, Troy -----Original Message----- From: Christopher Faylor [mailto:cgf AT redhat DOT com] Sent: Friday, May 04, 2001 2:42 PM To: 'cygwin AT cygwin DOT com' Subject: Re: Brainstorming a fix for CTRL-C handling in an emacs shell buf fer (non-TTY) On Fri, May 04, 2001 at 01:25:36PM -0600, Troy Noble wrote: >Is that patch in the latest sources? Yes. That is what I meant when I said "I've checked in a fix." Btw, you can answer this question by looking at the ChangeLog. I appreciate your tracking this down further but I don't see any reason to add a special environment variable. I will check in another change in the next hour or so. If you could check this out and see if it fixes your problem, I would appreciate it. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple