X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Message-ID: <4C6C39A8.6000402@cwilson.fastmail.fm>
Date: Wed, 18 Aug 2010 15:51:04 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
Reply-To: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: "run" changes behavior with cygwin-17.6
References: <20100818150920.GY11340@calimero.vinschen.de> <4C6C1490.3040202@cwilson.fastmail.fm> <4C6C1582.1080801@acm.org> <20100818182412.GA22698@ednor.casa.cgf.cx> <AANLkTikBTgg9M=xuZ4S2VkNU+Zr=hy3C=_Tr8BPj5baD@mail.gmail.com> <20100818185421.GC22698@ednor.casa.cgf.cx> <20100818191340.GB11340@calimero.vinschen.de> <20100818191906.GD22698@ednor.casa.cgf.cx> <20100818192238.GA27567@ednor.casa.cgf.cx> <20100818193446.GC11340@calimero.vinschen.de> <20100818194152.GE11340@calimero.vinschen.de>
In-Reply-To: <20100818194152.GE11340@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 8/18/2010 3:41 PM, Corinna Vinschen wrote:

> Chuck, btw., the function setup_win_environ() in run.c can easily be
> replaced with `cygwin_internal (CW_SYNC_WINENV);'

Yes, I was just looking at that. I think setup_win_environ (or its guts 
before some early refactoring) pre-dated CW_SYNC_WINENV.

Before removing it, I'll have to verify some things -- like whether 
that-cygwin-fork-we-don't-mention has CW_SYNC_WINENV, and how hard it 
would be to add if not -- since I want run to work "over there" too.


With respect to the orginal discussion that spawned this thread, I'm 
going to hold off on any changes to run/run2/cygutils until a consensus 
is reached regarding:
   1) what's going to happen "inside" cygwin wrt win32 cwd;
   2) what new APIs are provided
   3) and a project on how soon an official 1.7.7 will be released with
      those changes
and then evaluate how best to modify the client apps.

--
Chuck

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

