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, 11 Jul 2002 09:00:54 -0700 From: Dario Alcocer To: cygwin AT cygwin DOT com Subject: Re: close cygwin window - bash doesnt save history Message-ID: <20020711090054.B9120@ns.helixdigital.com> References: <20020711062601 DOT 15635 DOT qmail AT email DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020711082822 DOT 02b8e770 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <5.1.0.14.2.20020711082822.02b8e770@pop3.cris.com>; from rrschulz@cris.com on Thu, Jul 11, 2002 at 08:48:54AM -0700 On Thu, Jul 11, 2002 at 08:48:54AM -0700, Randall R Schulz wrote: > Dario, in investigating why Shane might not be having success with your > technique, I tried it both with and without the presence of the "tty" > option in the CYGWIN environment variable. (Without is my preferred > operating mode.) I discovered that the SIGHUP handler is _not invoked_ when > the "tty" option _is_ used. (My hypothesis had been the opposite, > actually.) I assume this means that the SIGHUP itself is not delivered when > the close box is clicked and "tty" mode is in effect. I'd say try putting the logout command in your SIGHUP handler and see if it behaves any differently. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. alcocer AT helixdigital DOT com -- http://www.helixdigital.com -- 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/