This is the mail archive of the
mailing list for the Cygwin project.
Re: Why rxvt?
- From: Michael A Chase <mchase at ix dot netcom dot com>
- To: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>, Cygwin list <cygwin at cygwin dot com>
- Date: Thu, 19 Sep 2002 18:47:03 -0700 (Pacific Daylight Time)
- Subject: Re: Why rxvt?
- References: <NEBBKHCFDGIGIJEHDJFCAEHFEBAA.firstname.lastname@example.org>
On Thu, 19 Sep 2002 17:17:45 -0700 "Paul D. DeRocco" <email@example.com> wrote:
> Can anyone tell me what advantages this might have for running bash,
> compared to the usual Windows command line window? I noticed in the readme
> that rxvt can leave child processes running if you close the window, which
> is scary since that's how I habitually terminate a command line session.
Don't do that. It's best to shut down any program as gracefully as it can.
For command line windows, that is by using the appropriate exit command.
Rxvt you gives better control over the window, especially in Win9x,
keyboard, cut-and-paste, scrollbars, resizing, fonts, and colors in
In WinNT and it's descendents, I've been perfectly happy using the console
window though in WinXP I've found it useful to call bash.exe directly
rather than via cygwin.bat to avoid having cmd.exe respond on exit to any
Ctrl-C's I've pressed during the session.
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html