From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: MinTTY "vs" rxvt (was Re: MinTTY 0.3.3)
Date: Mon, 12 Jan 2009 00:42:00 -0000 [thread overview]
Message-ID: <20090112003630.GC21040@ednor.casa.cgf.cx> (raw)
In-Reply-To: <496A54F6.7020107@cwilson.fastmail.fm>
On Sun, Jan 11, 2009 at 03:22:14PM -0500, Charles Wilson wrote:
>Christopher Faylor wrote:
>> Just to contribute something useful: Chuck Wilson, if you are reading
>> this, am I correct in assuming that you don't enjoy maintaining the
>> Windows version of rxvt?
>
>Well, it's my main terminal. I tried MinTTY and I'm not sure yet whether
>it will supplant rxvt for my personal use, but it shows promise.
>
>> If so, should we consider deprecating rxvt in
>> favor of MinTTY when MinTTY becomes a real package?
>>
>> If not, there is no harm in keeping two packages in the distribution. I
>> was just trying to lighten your load if you were interested.
>
>I'd lean toward keeping both in the distro (mainly because I'd hate to
>see a never-ending flood of "where'd rxvt go?" queries. That'd be more
>of a pain than the relatively infrequent updates that rxvt gets).
Yeah, that would be annoying.
Does rxvt actually get updated these days? I visited rxvt.org but that
site obviously hasn't seen any obvious love in a long time.
>I'd certainly be one of the first encouraging new (and old) cygwin users
>to try MinTTY if they dislike the standard cmd console, don't want to
>use X, and are aware of the pty issue.
>
>> The other thing that I've always wanted was some way for the user to
>> choose what they want to run without running cygwin.bat by hand. I
>> think that would mean setup.exe modification though.
>
>You mean like another setup.exe pane (or option in an existing pane) to
>select the terminal that should be started by the "default" Cygwin link
>in the Start Menu? That's an interesting idea...
Something like that. I used the word "running" too many times above but
what I was thinking was that we should use run login.exe on the desktop
and it should pick your startup program of choice.
>cgf: hmm...how's that for "lightening my load"? <g> Actually, this plan
>^^^^^^ is a lot of work up front but would probably be extremely
>low-maintianence after that.
But it sounds like a nice way to go...
cgf
--
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/
next prev parent reply other threads:[~2009-01-12 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 4:56 pedantic/misled/confused/passive-aggressive " Christopher Faylor
2009-01-11 9:17 ` Yaakov (Cygwin/X)
2009-01-11 20:53 ` MinTTY "vs" rxvt " Charles Wilson
2009-01-11 22:18 ` Andy Koppe
2009-01-11 23:33 ` Charles Wilson
2009-01-12 0:37 ` Andrew DeFaria
2009-01-12 0:45 ` Christopher Faylor
2009-01-12 0:42 ` Christopher Faylor [this message]
2009-01-12 5:14 ` Paul McFerrin
2009-01-12 12:35 ` Andy Koppe
2009-01-12 16:34 ` cgf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090112003630.GC21040@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).