This is the mail archive of the
mailing list for the Cygwin project.
Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]
- From: ericblake at comcast dot net (Eric Blake)
- To: cygwin at cygwin dot com
- Cc: David Rothenberger <daveroth at acm dot org>
- Date: Tue, 10 May 2005 17:06:33 +0000
- Subject: Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]
> I get ^H in a cmd window, an rxvt window, and an xterm window.
Hmm, it's been more than 1.5 years since I got cygwin working how I like it, so I don't remember exactly what I did, but these lines in /etc/profile are helpful:
# Consistent BackSpace and Delete Configuration:
$ for term in cygwin xterm rxvt ; do
> infocmp cygwin | grep kbs
shows that my terminfo database still claims the backspace key is currently ^H for all three terminals, even though I seem to recall trying to change kbs=^? at one point.
Ahah - I think I found it - in my ~/.Xdefaults, I added
*VT100.Translations: #override \
*ttyModes: erase ^?
At any rate, setting `stty erase '^?'' when backspace generates ^H is the wrong thing to do. And if it is possible, it would be much nicer if cygwin could distinguish between [ctrl-h] and [backspace], so that the two keys can be distinguished (it is nice to have [ctrl-h] be help, and [backspace] be a deletion command, in terminal-based emacs). And it would be really nice if the terminfo and termcap databases accurately reflected the true nature of the cygwin terminal, as to which sequences are needed to affect the screen and which sequences should pass through to the application.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html