summaryrefslogtreecommitdiff
path: root/t/t5100/rfc2047-info-0005
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2016-06-01 03:04:26 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-06-01 08:04:08 -0700
commitd2554c7207896136ad2033776efd29578592a3fb (patch)
treefaa6f8982fe08b87b0833f135a799c822d29e037 /t/t5100/rfc2047-info-0005
parentMore topics for 2.8.4 (diff)
downloadtgif-d2554c7207896136ad2033776efd29578592a3fb.tar.xz
test-lib: add in-shell "env" replacement
The one-shot environment variable syntax: FOO=BAR some-program is unportable when some-program is actually a shell function, like test_must_fail (on some shells FOO remains set after the function returns, and on others it does not). We sometimes get around this by using env, like: test_must_fail env FOO=BAR some-program But that only works because test_must_fail's arguments are themselves a command which can be run. You can't run: env FOO=BAR test_must_fail some-program because env does not know about our shell functions. So there is no equivalent for test_commit, for example, and one must resort to: ( FOO=BAR export FOO test_commit ) which is a bit verbose. Let's add a version of "env" that works _inside_ the shell, by creating a subshell, exporting variables from its argument list, and running the command. Its use is demonstrated on a currently-unportable case in t4014. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5100/rfc2047-info-0005')
0 files changed, 0 insertions, 0 deletions