This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Keyboard problems


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:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]