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:	<008b01c26afd$0d07a470$2a00a8c0@dash>
From:	"Kris Warkentin" <kewarken AT qnx DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	unintended logout with bash shell
Date:	Thu, 3 Oct 2002 12:50:59 -0400
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

This has been bugging me for a while and I think I've finally got it to a
repeatable case.

Suppose I have a function in my .profile like so:

 vi(){
  /cygdrive/d/vim/vim60/gvim.exe `for file in $* ; do cygpath -w $file ;
done` &
 }

If I do something like 'vi /usr/include/std<tab>' (<tab> for command
completion), as soon as it returns to the prompt (immediately because of the
'&'), the terminal says 'logout'.  As soon as I exit the last gvim running
on this terminal, the terminal goes away.  It seems more repeatable if the
command completion didn't work the first time, that is, not enough had been
typed to complete yet.

Anyone else seen this behaviour?

Kris


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