Re: How to handle length limit of PATH environment variable
- Date: Fri, 6 Apr 2018 03:20:35 +0300
- From: Andrey Repin <anrdaemon@xxxxxxxxx>
- Subject: Re: How to handle length limit of PATH environment variable
Greetings, Achim Gratz!
> Andrey Repin writes:
>> Partial solution could be a wrapper that reduce PATH length by dropping
>> nonessential/duplicate/Win-specific paths before invoking Cygwin terminal.
>> I have such a wrapper for my own reasons.
> You don't need one if your login shell is a POSIX shell and you don't
> use Windows applications if you have set a system or user variable
> CYGWIN_NOWINPATH to a non-empty value.
What if I explicitly do not want to do that?
It reduces interoperability to miniscule levels.
> It's usually way easier to add to a clean path than removing cruft and I
> generally lean into the direction of using wrapper scripts for Windows
> applications that I need to use from Cygwin since quite often some other
> things need attention aside from PATH.
For me, it's easier to wrap Cygwin apps, since I have sane wrapping material
(and many Cygwin tools not requiring any wrapping to begin with).
With best regards,
Friday, April 6, 2018 03:18:18
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple