On 2015-12-11, Bram Moolenaar <[email protected]> wrote: > The name user preferences was not quite right, but you can see that > these values will remain the same no matter what command you run. As > soon as you have something like: > > setenv SOME_VAR=some_value > run command > setenv SOME_VAR=
env SOME_VAR=some_value command_name Or, in most shells, just: SOME_VAR=some_value command_name > Then there is something wrong. In the case of SOURCE_DATE_EPOCH it's > really passing a value to the command being run, and that is not right. Every process has its own environment, normally inherited from the parent. I suspect the reason they chose environment variables was so that they can be passed to the top-level build process and picked up by some subprocess within the build, without the top-level process having to care about it or explicitly pass it down the line. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
