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 Message-ID: <008b01c26afd$0d07a470$2a00a8c0@dash> From: "Kris Warkentin" To: Subject: unintended logout with bash shell Date: Thu, 3 Oct 2002 12:50:59 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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' ( 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/