Timeline for Executing bash shell scripts
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2014 at 1:03 | vote | accept | JohnMerlino | ||
| Mar 14, 2014 at 0:54 | answer | added | Gilles 'SO- stop being evil' | timeline score: 0 | |
| Mar 14, 2014 at 0:13 | answer | added | Hauke Laging | timeline score: 0 | |
| Mar 14, 2014 at 0:11 | answer | added | alexgauss1994 | timeline score: 0 | |
| Mar 14, 2014 at 0:08 | comment | added | Hauke Laging |
I thought the most important method for executing shell script was calling them with their complete (possibly relative) path: ./this/is/my/script.sh. Furthermore you can create an alias to the full path so that you need not modify $PATH. And after exiting a subshell nothing is cleaned up: The calling shell's environment never was affected.
|
|
| Mar 13, 2014 at 23:56 | history | edited | Gilles 'SO- stop being evil' |
edited tags
|
|
| Mar 13, 2014 at 23:34 | history | asked | JohnMerlino | CC BY-SA 3.0 |