ITP: rxvt-W

Corinna Vinschen corinna-cygwin@cygwin.com
Tue Mar 21 15:55:00 GMT 2006


On Mar 21 10:13, Igor Peshansky wrote:
> On Tue, 21 Mar 2006, Corinna Vinschen wrote:
> > ...how do you plan to replace the old rxvt functionality from the user's
> > perspective?  This I don't see in your description.  So far the user can
> > call just "rxvt" and gets what the DISPLAY variable suggests.  With
> > rxvt-unicode you will get two binaries which can't (or rather,
> > shouldn't) use the same name.  Will "rxvt" in the long term be the X11
> > version or the W11 version?  Or will rxvt become a wrapper script
> > calling the "right" version depending on the DISPLAY setting to maintain
> > the current usability?
> 
> That shouldn't be hard.  The current rxvt is pretty simple-minded about
> when it uses native mode.  In particular, it tests for $DISPLAY (or the
> -display argument) being empty or exactly ":0", and runs in native mode,
> otherwise it tries to connect to an X server on that display.  This could
> be easily implemented in a wrapper script that parses the options and the
> value of $DISPLAY and exec's rxvt-unicode-W or rxvt-unicode-X.

Yeah, the technical details aren't on the overly tricky side, I'm just
asking Charles how he is planning to do it.


Corinna

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



More information about the Cygwin-apps mailing list