Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 19 Sep 2002 18:47:03 -0700 (Pacific Daylight Time) From: Michael A Chase Subject: Re: Why rxvt? To: "Paul D. DeRocco" , Cygwin list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE References: In-Reply-To: On Thu, 19 Sep 2002 17:17:45 -0700 "Paul D. DeRocco" 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 particular. 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. -- Mac :}) ** 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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/