This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
- From: "cyg Simple" <cygsimple at gmail dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 13 Jan 2015 09:37:03 -0500
- Subject: RE: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 20141217131626 dot GR10824 at calimero dot vinschen dot de> <87oaqynpzq dot fsf at Gertrud dot fritz dot box> <20150107174122 dot GB4190 at calimero dot vinschen dot de> <20150108171825 dot GB15791 at calimero dot vinschen dot de> <8761cez7qi dot fsf at Rainer dot invalid> <20150112103834 dot GA15213 at calimero dot vinschen dot de> <loom dot 20150113T124708-54 at post dot gmane dot org> <20150113125648 dot GV15791 at calimero dot vinschen dot de> <loom dot 20150113T135909-484 at post dot gmane dot org> <20150113135339 dot GW15791 at calimero dot vinschen dot de> <loom dot 20150113T150342-521 at post dot gmane dot org>
> -----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