DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=hjyzVzHEwk3Vp9WWGGenyzfmbJkqD+Q1w4rvKWbzfnU
	vXP6xrZEoau1tAgPefX0y4HHP7220y2ox60HgTk86qy07frSbqQdSc44/TJTGZu9
	EPCwYkuZ0Y2VgA4QUu1Zl1wJAW+CIq39anRTn+fPPISoKipZezAA+Y4W5tcdHqeM
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "cyg Simple" <cygsimple@gmail.com>
To: <cygwin@cygwin.com>
References: <announce.20141217131626.GR10824@calimero.vinschen.de> <87oaqynpzq.fsf@Gertrud.fritz.box> <20150107174122.GB4190@calimero.vinschen.de> <20150108171825.GB15791@calimero.vinschen.de> <8761cez7qi.fsf@Rainer.invalid> <20150112103834.GA15213@calimero.vinschen.de> <loom.20150113T124708-54@post.gmane.org> <20150113125648.GV15791@calimero.vinschen.de> <loom.20150113T135909-484@post.gmane.org> <20150113135339.GW15791@calimero.vinschen.de> <loom.20150113T150342-521@post.gmane.org>
In-Reply-To: <loom.20150113T150342-521@post.gmane.org>
Subject: RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
Date: Tue, 13 Jan 2015 09:37:03 -0500
Message-ID: <04ae01d02f3e$7eb2f6c0$7c18e440$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Achim Gratz
> 
> Corinna Vinschen  writes:
> > Which means what for the Cygwin DLL?  Dropping TMP/TEMP from the
> > merged Windows env?  It makes sense, I think.  Of course, there will
> > be others...

My process is dependent on the fact that TMP/TEMP have in/out rewriting of
strings from POSIX to WINDOWS so please leave it as is.

> 
> Just for this question: if the Cygwin DLL always handles it no matter
what, then I
> think these should be dropped.  If they aren't dropped, I'd say at least
sshd
> would need to override them.  I don't want to enable PermitUserEnvironment
> just to deal with these two and sshrc can't be used to change the
environment.
> Another idea would be to prefix WIN_ to all inherited variables so any
Cygwin
> program wanting to use them could pull them in as needed.
> 

And I have a mashup of Cygwin and Windows applications.  I use Cygwin as a
tool for Windows applications not a replacement of the Windows applications.

> As I said, I'm trying to keep Cygwin and its environment separate from
Windows
> as much as possible, but others have different ideas about this and would
> probably want the opposite.  Maybe some CYGWIN setting would allow to do
> one or the other as needed (or always do it, but control the prefix), but
that's of
> course extra code to maintain and test.
> 

I suppose a CYGWIN environment option could  control  the result with the
default being the current actions.

--
cyg Simple


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