Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Matched-Lists: []
Message-ID: <138390-2200510420205635532@cantv.net>
Reply-To: rodmedina AT cantv DOT net
From: "Rodrigo Medina" <rodmedina AT cantv DOT net>
To: cygwin AT cygwin DOT com
Subject: Bug in rxvt.bat (Was: rxvt malfunctioning with us-laptop keyboard)
Date: Thu, 20 Oct 2005 16:56:35 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
X-Virus-Status: Clean

Hi,
In a previous message I reported that rxvt was converting Shift-h to
Ctrl-h. It was not so. The problem is due to a bug in rxvt.bat and to
the peculiar way rxvt handles the BackSpace key.
In rxvt without options the BackSpace key yields "^?" and Crtl-BackSpace
yields "^H". In the shell `stty -a'  says `erase = ^?', BUT ALSO ^H erases.
Giving `stty sane' sets `erase = ^H', then only ^H erases (Crl-h or
Ctrl-BackSpace). If one sets `stty erase ^?', then only BackSpace, that
yields "^?", erases.
In rxvt.bat there is the option `-backspacekey ^H', but actually the
Windows cmd-shell filters the "^" symbol and one gets that the BackSpace key
and the Ctrl-BackSpace key actually yield "H", but rxvt also modifies stty,
so `stty -a' says `erase = H', but as in the original case also Ctrl-h
erases.
If one gives `stty sane' one sets `erase = ^H', one can verify that
Shift-h, BackSpace and Ctrl-Backspace yield "H". One may erase with Ctrl-H.

Solution: Put in rxvt.bat `-backspacekey "^H"'

Bye
R.M.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/