Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-Id: <5.1.0.14.2.20020822132037.0289ef30@pop3.cris.com>
Date: Thu, 22 Aug 2002 13:34:04 -0700
To: cygwin@cygwin.com
From: Randall R Schulz <rrschulz@cris.com>
Subject: Re: Keyboard problems
In-Reply-To: <3D654010.3060305@hekimian.com>
References: <F33mOweivHsvu4HAQSo00009818@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Joe,

And as I have recently learned, the "tty" option in the CYGWIN environment 
variable is a rather "fine-grained" attribute, so even if you don't 
generally (like to) run with the tty option set, you can invoke Emacs thusly:

CYGWIN="tty $CYGWIN" emacs

And have the tty mode apply only to Emacs.

However, when you exit emacs, the tty driver is out of kilter (perhaps it's 
the readline library that's out of kilter w.r.t. the tty driver, I don't 
really know). To resolve this issue, something like this in your 
"~/.bashrc" might work well for everyday use:

EMACS="$(which emacs)"
emacs() {
         TTY_MODES="$(stty -g)"
         CYGWIN="tty $CYGWIN" "$EMACS" "$@"
         stty "$TTY_MODES"
}


By the way, Joe, is the "binmode" essential to resolving Tim's problem? I 
use binmode routinely, but is it relevant to the problem with Emacs 
sequences that include CTRL-C or other signal-generating keys when "tty" is 
not set?


Randall Schulz
Mountain View, CA USA


At 12:48 2002-08-22, Joe Buehler wrote:
>Tim Chartier wrote:
>
>>Later, I ran emacs and it did not understand C-x C-c to exit.
>
>Set a system environment variable CYGWIN on your Windows machine
>with value "tty binmode" (no quotes).
>
>Joe Buehler


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/