X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=tfMrVVat7Cm3Y12vXoJXHUGoLxdjGIDzFXyquGeVSFr9/mLi3xJ3C F4+nWr6pHA6pJAv+TuKKgBuuGVUs8LgJza9Biz7nEjDPNGMdQp9PXlPUW6rgKhac MLSoZ4TBVL6AbNcZDwBT1/xJTKjzrgelJ+a1l3M24Hgix2dbNrWDLk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=nHmKbPny1x+TF7dgT6g0U6WvSrk=; b=RZkQboYpj+G227z82NJFr25VXaGR el/dNSH0L4Aej3ucsDKdk54LxftZR6ZGQSRrMlUKaW16esDgKFlM5hjMK2c4rcyh /FQiDOUAk1jcdhpAvll7PgMbsSKMAxAnLGpamyTdsusNwrQffwYE4VifwHW7Jxi/ GL+hUc7C2pKJn/s= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Date: Tue, 13 Jan 2015 16:47:19 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release) Message-ID: <20150113154719.GX15791@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <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> <20150113125648 DOT GV15791 AT calimero DOT vinschen DOT de> <20150113135339 DOT GW15791 AT calimero DOT vinschen DOT de> <04ae01d02f3e$7eb2f6c0$7c18e440$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mejza3ZMMA5Za1mX" Content-Disposition: inline In-Reply-To: <04ae01d02f3e$7eb2f6c0$7c18e440$@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) --mejza3ZMMA5Za1mX Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Jan 13 09:37, cyg Simple wrote: > > -----Original Message----- > > From: Achim Gratz > >=20 > > 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... >=20 > 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. You're missing something here. What we're talking about is a merge of the user's Windows default environment at the time of a user context switch (for instance, logon via ssh). In that case, "leaving it as is" today would mean to *drop* TMP/TEMP from the environment, because that's what ssh does anyway. Ssh drops almost everything from the environment, before exec'ing the child process. And that's a good thing, because the environment (e.g. LOCALAPPDATA, USERPROFILE, etc) would otherwise reflect the settings of the user running the sshd service, not the settings of the user just logging in. The new functionality we're talking about here is that the next Cygwin would "resurrect" the Windows environment setting for the child process started by sshd. And these settings would be the one for the user just logging in. This would help some Windows applications which otherwise choke if these Windows environment variables are missing. Having said that, TMP/TEMP have the downside of being used by POSIX and Windows applications alike. Therefore these variables usually are converted from Windows to POSIX and vice versa on the fly. However, whether it makes sense to set TMP/TEMP in a ssh logon session or a cron session is questionable. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --mejza3ZMMA5Za1mX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUtT4HAAoJEPU2Bp2uRE+gmsoP/1YxUlttElu6gQzGEyPO52Q3 kqWxRGMDUqkqhIuo9djYSnPAX3hm/uva7yDviyvKMgDPfAb0LQryH4CgwycLNut3 Mp5ixhRKocJ2fe6g26yvKa82pj7aQXLzwLhfS0zvexJpA10UHQDlA/H//s+6Fu9l eW+PTFu512cnzKeef8kxVRPlK031KtdCC/IR1jJMmvEBliyxckoXOHUvk9yLHMj3 IqEKApCGUC8uvjmoFPQvJ6uUsk1q5Sw0xmDVuWtjI2vWJG15DWQj7yvW7TxcBMTq tRxJD0EcWa/PiSTkctmYHLqPE+0yy37IK+LBoJr50EkC+S/f8DBY8hS3a6RTnrMA 0hbpRdsiPAK9VZMNcHPlClCbCZ0F10TFJ4CuZOnW8pZ0WqkBGbCeH6ZuKASJAC0U hJxbG8jKoosxIcx1O4bALoPZmglmwMbNR8HODSQM10xYAcWymdj1S4usVNBO9hHQ Axb87mCvj8BeulQCCf5vwbJu50GyrnAdU63k6EoILlCcpUsFH853cfwluGiOYv9s B/kgf3g3whKkJlqUWoA7GeKba3t0nAFjp1abkGKuhjUebpmKqaEyre+XsNZyIgAB 3EgoW/E6yQEG6dOFRwwym4Fw0Z/kTHRh3+uv+d34BxjX6Ss5fTXQjN4PdttLqip3 tdJ/D+qP5alIzmF8WuE3 =Scrh -----END PGP SIGNATURE----- --mejza3ZMMA5Za1mX--