Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalBeing dependent upon Cygwin, how how about putting the command in your saved file, e.g.:
echo "export PATH=$PATH" > dat Then sourcing the script later to set the path:
. ./dat Note that "sourcing" the script (vs. just executing it) is required for it to modify your current environment - and not just new child environments.
Being dependent upon Cygwin, how how about putting the command in your saved file, e.g.:
echo "export PATH=$PATH" > dat Then sourcing the script later to set the path:
. dat Note that "sourcing" the script (vs. just executing it) is required for it to modify your current environment - and not just new child environments.
Being dependent upon Cygwin, how how about putting the command in your saved file, e.g.:
echo "export PATH=$PATH" > dat Then sourcing the script later to set the path:
. ./dat Note that "sourcing" the script (vs. just executing it) is required for it to modify your current environment - and not just new child environments.
Being dependent upon Cygwin, how how about putting the command in your saved file, e.g.:
echo "export PATH=$PATH" > dat Then sourcing the script later to set the path:
. dat Note that "sourcing" the script (vs. just executing it) is required for it to modify your current environment - and not just new child environments.