Greetings, Francis Litterio!
>>> 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 y
On Nov 17 12:11, Vince Rice wrote:
> > On Nov 17, 2016, at 12:04 PM, Francis Litterio wrote:
> >
> > On 9/8/2016 8:07 AM, Corinna Vinschen wrote:
> >> On Sep 5 10:36, Doug Henderson wrote:
> >
> >>> I set CYGWIN_NOWINPATH=1 in my user environment variables, i.e. in
> >>> registry, not in a cmd
> On Nov 17, 2016, at 12:04 PM, Francis Litterio wrote:
>
> On 9/8/2016 8:07 AM, Corinna Vinschen wrote:
>> On Sep 5 10:36, Doug Henderson wrote:
>
>>> 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
>>>
On 9/8/2016 8:07 AM, Corinna Vinschen wrote:
On Sep 5 10:36, Doug Henderson wrote:
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 pro
On Sep 5 10:36, Doug Henderson wrote:
> 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/sear
Doug Henderson writes:
[…]
> 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.
No, this is purely done in /etc/profile, cygwin1.dll has nothing to do
with it.
Regards,
Achim.
--
+<[Q+ Matrix-12
Jim Reisert AD1C writes:
> 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.
I now see what's wrong. 'ORIGINAL_PATH' in my shell environment was
so long, I missed the very short 'PATH'. So it is working just fine.
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentati
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_US
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
> emai
10 matches
Mail list logo