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 Date: Thu, 12 May 2005 11:59:15 -0700 From: David Rothenberger Subject: Re: Patch for cygutils: make cygstart behave better under mount -X In-reply-to: <20050512185428.GE478@trixie.casa.cgf.cx> To: cygwin AT cygwin DOT com Message-id: <4283A783.6070801@acm.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <42839F26 DOT 809 AT mscha DOT org> <20050512185428 DOT GE478 AT trixie DOT casa DOT cgf DOT cx> User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On 5/12/2005 11:54 AM, Christopher Faylor wrote: > On Thu, May 12, 2005 at 08:23:34PM +0200, Michael Schaap wrote: > >>Hi, >> >>Attached is a patch to fix cygstart behaviour when running under "mount >>-X". Cygstart now ensures that the Windows environment is synchronized >>with the Cygwin one. >>(For more details, see the recent thread: "Fixing strace and cygcheck so >>that they work with mount -X") >> >>Chuck, can you, at your convenience, apply this patch and release a new >>version of cygutils? > > > Didn't we come to the conclusion that you shouldn't be adding PATH to > the environment? I don't see anything which does this in your patch. It's done indirectly by not copying cygwin variables that already exist in the Windows environment. Is it safe to assume that PATH will always already been in the Windows environment given a cygexec invocation? If not, we'll need to copy it and convert it to Windows form. -- David Rothenberger spammer? -> spam AT daveroth DOT dyndns DOT org GPG/PGP: 0x7F67E734, C233 365A 25EF 2C5F C8E1 43DF B44F BA26 7F67 E734 If money can't buy happiness, I guess you'll just have to rent it. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/