Greetings, Achim Gratz! > a) Just warn about the missing PATH component without changing the PATH. > b) Give the user an option to let the command run with a separate PATH.
> Indeed there might be other things that are missing in the environment, > so instead of just fixing up PATH you might consider using a wrapper > that the user can change. This is an interesting point. Probably letting the user specify custom $PATH for quick commands (and save current %PATH% as $ORIGINAL_PATH) may be the best choice. The default can be %Cygwin%\bin:%PATH% or %PATH%:%Cygwin%\bin, I'm not very concerned as long as it's explicit and customizable. If anybody need a wrapper, they may write and use it by themselves. (I already have one, written in TCC, working quite well.) -- With best regards, Andrey Repin Friday, December 7, 2018 0:15:56 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
