Skip to main content
17 events
when toggle format what by license comment
S Oct 7, 2015 at 1:32 history bounty ended cuonglm
S Oct 7, 2015 at 1:32 history notice removed cuonglm
Oct 6, 2015 at 1:57 vote accept cuonglm
Oct 5, 2015 at 19:35 comment added Stéphane Chazelas @muru, yes, and other non-POSIX shells. Like rc that allows anything in a variable name (and where all variables are exported).
Oct 5, 2015 at 19:29 comment added Stéphane Chazelas Related: Is there a difference between prepending a name-value-pair to a command and using env in bash?
Oct 5, 2015 at 19:24 answer added Mark Plotnick timeline score: 5
Oct 5, 2015 at 19:21 history tweeted twitter.com/StackUnix/status/651114942540595201
S Oct 5, 2015 at 17:11 history bounty started cuonglm
S Oct 5, 2015 at 17:11 history notice added cuonglm Canonical answer required
Oct 2, 2015 at 11:10 answer added schily timeline score: 0
Oct 2, 2015 at 10:06 history edited cuonglm CC BY-SA 3.0
added 6 characters in body
Oct 2, 2015 at 7:35 comment added muru The shells can't access these variables, true. But why should that prevent a program written in C or Python from accessing them?
Oct 2, 2015 at 7:12 comment added cas virtualenv seems like a great re-implementation of DLL Hell. Programmers probably love it. Sysadmins generally hate it.
Oct 2, 2015 at 6:28 comment added cuonglm @cas: One usage of it was shown in my question, it allow you to define function in environment variable in bash.
Oct 2, 2015 at 5:19 comment added cas I don't see any use for it and IMO almost every use of env is a mistake.....especially including the python crowd's promotion of using env on the #! line of a script file. See unix.stackexchange.com/questions/29608/… for interesting debate on the topic.
Oct 2, 2015 at 4:45 history edited cuonglm CC BY-SA 3.0
added 13 characters in body
Oct 2, 2015 at 4:23 history asked cuonglm CC BY-SA 3.0