Re: CYGWIN_NOWINPATH (was Re: /etc/profile: avoid multiple /usr/bin in PATH)

[Doug Henderson <djndnbvg at gmail dot com>]

On 5 September 2016 at 10:04, Jim Reisert AD1C  wrote:
> On Sun, Sep 4, 2016 at 10:07 PM, Doug Henderson wrote:
>
>> Note that CYGWIN_NOWINPATH is still undocumented, except in the email
>> archives. See, e.g.
>>
>>     https://www.google.ca/search?q=CYGWIN_NOWINPATH+site:cygwin.com
>>
>> CYGWIN_USEWINPATH is also undocumented, except in a non-cygwin.com
>> email archive.
>
> CYGWIN_NOWINPATH is not working for me.
>
> CYGWIN_NT-10.0-WOW AD1C 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 Cygwin
>
> d:\>printenv | grep CYG
> CYGWIN=nodosfilewarning
> CYGWIN_NOWINPATH=1
>
> When I start bash, I still get my full Windows path as part of the
> bash path.  Am I missing something?
>
> I have neither a ~/.login or ~/.profile, only a ~/.bashrc

I set CYGWIN_NOWINPATH=1 in my user environment variables, i.e. in
registry, not in a cmd shell. I expect it needs to be seen when the
first cygwin1.dll instance starts, so you would need to stop all
cygwin processes and servers, just like you do when you run the cygwin
setup, for this to be effective.

It works for me in both my x86_64 and x86 cygwin installs. I start
bash from mintty using the desktop shortcut created by setup (or a
copy of it), I have CYGWIN=error_start=d:\cygwin64\bin\dumper.exe, I
know this is the wrong dumper for my 32bit install, but I do almost
all my work in the 64 bit install, that's not a big deal for me.

BTW: I think cygwin1.dll stores the original windows path in the
exported ORIGINAL_PATH variable. I am running Windows 7 Home Premium
on an laptop.

$ uname -a
CYGWIN_NT-6.1 Rover 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin


HTH
Doug



-- 
Doug Henderson, 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