DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:subject:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=gWa
	uulhiRM7UbQbCdt/ViP7MI8JyE1WLk6v9g9y/f4zQW5Y9bjNjcfNszbc9bbOLZJT
	UT7a5aM3NjrTmxYSQiM6h3u0T5Ypi1zAC6cVmaJM+N8TorjXOuly5+HDlthpsjTm
	VI7/3VBZsuYQRdv5Dkk8yC5LrtTsq0Ow+oIUde48=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 24 Dec 2015 03:12:36 -0500
From: qrasmfu8f4 AT snkmail DOT com
To: cygwin AT cygwin DOT com
Message-ID: <26785-1450944756-673263@sneakemail.com>
Subject: rxvt for cygwin64?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I've been using cygwin's rxvt (without X) for years, and prefer it to mintty both because I use rxvt on all my linux machines and because I've never liked putty.  Despite most (but not all) of my Windows machines running 64-but windows7, I've procrastinated on switching to cygwin64, but I recently had to replace my laptop with a new Windows 10 machine, and figured I might as well install cygwin64.  Everything went well until I discovered rxvt is not available in 64-bit.  I found this thread (https://cygwin.com/ml/cygwin/2013-09/msg00016.html) from 9/2013 in the archives, but there doesn't seem to have been any resolution.

Is there any plan to port rxvt to cygwin64?
If not, does anyone have any hints so I can try it myself (I have 35 years of system software development experience, but I never worked on any cygwin software)?

    thanks,
    Peter


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