Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.1.0.14.2.20020711091049.0209f770@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Thu, 11 Jul 2002 09:42:41 -0700
To:	Dario Alcocer <alcocer AT helixdigital DOT com>, cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	Re: close cygwin window - bash doesnt save history
In-Reply-To:	<20020711090054.B9120@ns.helixdigital.com>
References:	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020711082822 DOT 02b8e770 AT pop3 DOT cris DOT com>
	<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

Dario,

It works great for me just as you suggested (*). I don't like using "tty" 
mode, so there's no issue for me. I was thinking perhaps it didn't work for 
Shane because he might be using "tty" mode.

However, if the SIGHUP doesn't get delivered (in "tty" mode), there's 
really no hook to hang this technique upon, it seems.


(*) In further investigating options using "trap," I discovered I can no 
longer repeat my earlier success, regardless of whether I use "tty" or not.

There's something odd afoot here. When and if I figure out more, I'll 
report back.

Randall Schulz
Mountain View, CA USA


At 09:00 2002-07-11, Dario Alcocer wrote:
>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


--
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/

- Raw text -