Greetings, Achim Gratz! > Andrey Repin writes: >> P.P.S. >> 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. If-if-if. 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, Andrey Repin Friday, April 6, 2018 03:18:18 Sorry for my terrible english... -- 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
