Re: RXVT doesn't recognize ALT + Cursor keys

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Aug 20 13:59, Corinna Vinschen wrote:
> On Aug 20 04:25, Brian Dessent wrote:
> > Corinna Vinschen wrote:
> > 
> > > as before.  I'm going to use this patch locally anyway, but maybe that's
> > > one for inclusion upstream?
> > 
> > As far as I know, there is no upstream rxvt -- it's a dead project.  The
> > rxvt-unicode fork is where new development happens.  I'm not sure what
> > that means exactly for the W11/Win32 parts of rxvt.  I'm sure Chuck
> > could answer this a lot more definitively.
> 
> It makes still sense for Cygwin, isn't it?

I'm just a bit puzzled about the key codes.  By default, when rxvt is
invoked without explicitely setting the terminal name (-tn option),
rxvt is recognized as an xterm.  The cursor keys correctly return
ESC [ A to ESC [ D.  However, the Home and End keys return ESC [ 7 ~
and ESC [ 8 ~, while a real xterm returns ESC [ H and ESC [ F.

Ok, so I set the terminal to rxvt-cygwin-native as suggested in the
README file.

Now the Home and End keys are ok, because the termcap/terminfo entry
for these keys is matching.  However, the termcap/terminfo entries
expect ESC O A to ESC O D for the cursor keys but, as I wrote above,
rxvt returns the xterm sequences ESC [ A to ESC [ D, so the cursor
keys don't work anymore.

So the question is, how is that supposed to work?  Wouldn't it make
sense to change the escape sequences of Home and End key to their xterm
equivalents and drop the idea to set TERM to rxvt-cygwin-native?
At least this looks like the simpler approach, rather than changing
the termcap/terminfo entries of the world...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat