too many environment variables on self-compiled xar archiver
Brian Inglis
Brian.Inglis@SystematicSw.ab.ca
Thu May 25 17:37:00 GMT 2017
On 2017-05-24 15:18, Hans-Bernhard Bröker wrote:
> Am 24.05.2017 um 12:01 schrieb Andrey Repin:
>
>>> Did you notice this entry and does anyone know where this comes from?
>>> !C:=C:\cygwin\bin
>
>> This is coming from CMD, and denotes current working directory on an
>> indicated
>> drive.
>
> And for (most of) all the hairy details, see
>
> https://blogs.msdn.microsoft.com/oldnewthing/20100506-00/?p=14133
>
> If you see these, you must have printed the environment using a tool
> other than CMD itself (e.g. Cygwin's "env").
Or as comment
https://blogs.msdn.microsoft.com/oldnewthing/20100506-00/?p=14133#comment-830913
says, in cmd type
set "
to see all environment variables including those starting with "=".
So the above is Cygwin "cleaning" the inherited cmd environment which
contains =<d>:=<d>:\<wd> for each mapped drive, and some other legacy
compatible information, by changing the leading "=" to "!", so it can
restore it for child process environments.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
More information about the Cygwin
mailing list