From: Andy Piper <andyp@bea.com>
To: cygwin@cygwin.com
Subject: Re: When will cygwin ever be stable?
Date: Thu, 03 May 2001 17:10:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010503170146.00b58100@san-francisco.beasys.com> (raw)
Louis Bohm wrote:
> I do not know about the other points you made but I can tell you that
the scroll
> bars do work when you are running rxvt. Maybe you should try that instead.
So let me understand this, in order to get a functional terminal I have to
use a package that is not even shipped with the standard install? No
standard user is ever going to do this, they are just going to get hacked
off with it being broken. A better reason for using rxvt might be because
its faster.
Maybe everyone in the know uses rxvt and that's why the standard terminal
is not so great?
andy
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2001-05-03 17:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 17:10 Andy Piper [this message]
2001-05-03 17:22 ` Charles S. Wilson
2001-05-03 17:31 ` Andy Piper
-- strict thread matches above, loose matches on Subject: below --
2001-05-03 17:16 Andy Piper
2001-05-04 4:11 ` Earnie Boyd
2001-05-03 15:57 Robert Collins
[not found] <4.3.2.7.2.20010501101339.00eaa780@san-francisco.beasys.com>
2001-05-01 10:47 ` Andy Piper
2001-05-01 11:00 ` Louis Bohm
2001-05-01 11:43 ` egor duda
2001-05-01 12:06 ` Earnie Boyd
2001-05-03 5:38 ` Warren Young
2001-05-03 7:39 ` Larry Hall (RFK Partners, Inc)
2001-05-03 14:14 ` Robert Collins
2001-05-03 15:44 ` Christopher Faylor
2001-04-30 11:28 Andy Piper
2001-04-30 12:30 ` Christopher Dale Campbell
2001-04-30 12:43 ` Christopher Faylor
2001-04-30 20:31 ` Charles S. Wilson
2001-04-30 21:03 ` Christopher Faylor
2001-04-30 21:13 ` Charles S. Wilson
2001-04-30 21:28 ` Christopher Faylor
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=4.3.2.7.2.20010503170146.00b58100@san-francisco.beasys.com \
--to=andyp@bea.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).