Message-ID: <4B18602C.40600@tlinx.org>
Date: Thu, 03 Dec 2009 17:04:44 -0800
From: Linda Walsh <cygwin@tlinx.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 ThunderBrowse/3.2.6.8 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: (random:)Re: Why does exiting bash window kill off  Gvim? (Windows version, but X-would be same question)
References: <4B184E76.60909@tlinx.org>
In-Reply-To: <4B184E76.60909@tlinx.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

FWIW -- now cygwin is NOT killing off background processes.  I haven't even
installed new versions -- was just thinking about it -- MAN that is
FAST fixing!   ;-)


*sigh*...

I maintain that I continue to experience transient and non-repeatable
errors that defy explanation (on Win7).  It' might be Win7's auto
repair functionality changing the environment dynamically?  Just a 
thought.

I read that "it's a feature" for repairs to functionality to be made
in the background, automatically, when the system detects an application
not working.  They regard it as desirable if it does this correction
"silently".

Yeah...

Probably not that here, but whatever.  It's probably still true with x
progs, but they aren't where I left them. (gvim in particular)...

That's what I'm talking about -- things appear to show up in some 
locations but then are not there when I look later or in explorer.
Very disconcerting.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple