Timeline for Exporting environment variable
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 18, 2018 at 14:45 | history | edited | Rui F Ribeiro | CC BY-SA 4.0 | deleted 62 characters in body |
| Feb 26, 2012 at 5:41 | history | migrated | from stackoverflow.com (revisions) | ||
| Feb 25, 2012 at 3:22 | answer | added | kev | timeline score: 1 | |
| Feb 25, 2012 at 3:16 | answer | added | Krazy Glew | timeline score: 2 | |
| Feb 25, 2012 at 3:10 | comment | added | kev | Change double quote to single quote, then try: eval $hello | |
| Feb 25, 2012 at 3:05 | answer | added | Basilevs | timeline score: 0 | |
| Feb 25, 2012 at 2:58 | comment | added | Shahzad | I am simply specifying the name of the variable like $hello | |
| Feb 25, 2012 at 2:57 | comment | added | Daniel | How are you executing the command in the variable? Command substitution? | |
| Feb 25, 2012 at 2:01 | comment | added | Shahzad | Actually I want to setup the environment variable that will contain some code but will be executed in some other bash script. | |
| Feb 25, 2012 at 1:45 | comment | added | ruakh | Are you saying that echo $STY should print out the actual text for i in {0..3}; do echo $i; done? Or are you saying that echo $STY should execute that for-loop? (I ask because, although it sounds to me like the former, Borealid below seems to think you really want the latter.) | |
| Feb 25, 2012 at 1:42 | answer | added | Borealid | timeline score: 2 | |
| Feb 25, 2012 at 1:40 | history | asked | Shahzad | CC BY-SA 3.0 |