Timeline for In Bash, when to alias, when to script and when to write a function?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 17, 2018 at 8:50 | comment | added | nohillside |
@tripleee The meaning was more like "you can't exec() shell functions" :-)
|
|
| Aug 19, 2018 at 8:10 | comment | added | tripleee | It is not true at all that functions are "only available inside Bash". If you mean to say they are a Bash-only feature, that is simply false (Bourne shell and every compatible derivative has them); and if you mean to say they are a feature of interactive shells, that's not accurate either (though aliases, variables, and functions defined in a file which gets loaded at startup by interactive shells obviously will not be loaded by noninteractive shells). | |
| Jul 24, 2018 at 16:29 | comment | added | Martin - マーチン |
In alias command="bash bashscriptname" the script does not necessarily have to be executable; in the alias c=/path/to/script it has to.
|
|
| Feb 5, 2012 at 15:08 | history | answered | nohillside | CC BY-SA 3.0 |