Timeline for Why does FOO=bar; export the variable into my environment
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2019 at 3:58 | comment | added | Johan Myréen | Sorry, I should have posted this as a comment to the question, where Rothgar said that FOO was also "exported into my current shell environment." | |
| May 20, 2019 at 23:08 | history | edited | user232326 | CC BY-SA 4.0 |
added 3 characters in body
|
| May 20, 2019 at 22:43 | history | edited | user232326 | CC BY-SA 4.0 |
Typo
|
| May 20, 2019 at 22:12 | vote | accept | Justin Garrison | ||
| May 20, 2019 at 21:24 | history | edited | user232326 | CC BY-SA 4.0 |
Better description.
|
| May 20, 2019 at 21:19 | history | edited | user232326 | CC BY-SA 4.0 |
added 151 characters in body
|
| May 20, 2019 at 21:04 | history | edited | user232326 | CC BY-SA 4.0 |
Builtin effect.
|
| May 20, 2019 at 21:03 | comment | added | Kusalananda♦ |
Not knowing anything about Docker, I wonder if it would actually work if the -e FOO=$FOO thing (which I presume is used to set an environment variable) is removed since FOO is set in Docker's environment.
|
|
| May 20, 2019 at 21:01 | comment | added | Johan Myréen |
The variable FOO is also not exported to the current shell environment, but set as a shell variable, unless it has been previously exported.
|
|
| May 20, 2019 at 20:50 | history | edited | user232326 | CC BY-SA 4.0 |
added 402 characters in body
|
| May 20, 2019 at 20:43 | history | answered | user232326 | CC BY-SA 4.0 |