RE: rxvt problems - traps control codes

["Andrew Logue" <avlogue at home dot com>]

> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd@yahoo.com]
> Sent: January 24, 2001 6:51 AM
> To: Andrew Logue
> Cc: cygwin@cygwin.com
> Subject: Re: rxvt problems - traps control codes
>
>
> Andrew Logue wrote:
> >
> > This should be an easy one:
> >
> > I have rxvt running the win95 port of CMD.EXE.  However, ^C and
> the up/down
> > arrow keys are intercepted by rxvt, and not passed on to CMD.EXE.  As a
> > result, I cannot use doskey, even though CMD.EXE has loaded it.
>  Also, if I
> > run a batch file through cmd.exe I cannot terminate it with ^C,
> since this
> > terminates rxvt.
> >
> > Please help me fix this!!  I know very little about termcaps, TERM, etc.
> >
>
> The only fix, AFAIK, is for you to get the sources for rxvt, the xlib
> from Bub's distro and make it do what you want.  Rxvt was designed to
> control the UI so it isn't going to pass through the events of the
> Mouse.

Events of the mouse?  up/down arrows and control-c are keyboard commands -
I'm not sure I understand.  I just tried running bash via rxvt and the bash
command line history works with my arrow keys.  There's got to be a way to
get rxvt to pass these keysyms to the executed application instead of
handling them locally.  It passes normal keyboard characters to cmd.exe, so
why not ESC, control-C, etc?

Comments welcome.

TIA,
Andrew.



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple