From: Phillip Wood <phillip.wood123@gmail.com>
To: Eric Sunshine <ericsunshine@charter.net>, git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Rubén Justo" <rjusto@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH 1/4] t3430: modernize one-shot "VAR=val shell-func" invocation
Date: Mon, 22 Jul 2024 16:09:59 +0100 [thread overview]
Message-ID: <c586f7dc-636b-45a3-acb2-faedfe1068e6@gmail.com> (raw)
In-Reply-To: <20240722065915.80760-2-ericsunshine@charter.net>
Hi Eric
On 22/07/2024 07:59, Eric Sunshine wrote:
> From: Eric Sunshine <sunshine@sunshineco.com>
>
> Unlike "VAR=val cmd" one-shot environment variable assignments which
> exist only for the invocation of 'cmd', those assigned by "VAR=val
> shell-func" exist within the running shell and continue to do so until
> the process exits (or are explicitly unset).
I'm not sure I follow. If I run
sh -c 'f() {
echo "f: HELLO=$HELLO"
env | grep HELLO
}
HELLO=x f; echo "HELLO=$HELLO"'
Then I see
f: HELLO=x
HELLO=x
HELLO=
which seems to contradict the commit message as $HELLO is unset when the
function returns. I see the same result if I replace "sh" (which is bash
on my system) with an explicit "bash", "dash" or "zsh".
I'm also confused as to why this caused a problem for Rubén's test as
$HELLO is set in the environment so I'm don't understand why git wasn't
picking up the right pager.
> check-non-portable-shell.pl
> warns when it detects such usage since, more often than not, the author
> who writes such an invocation is unaware of the undesirable behavior.
>
> A common way to work around the problem is to wrap a subshell around the
> variable assignments and function call, thus ensuring that the
> assignments are short-lived. However, these days, a more ergonomic
> approach is to employ test_env() which is tailor-made for this specific
> use-case.
Oh, that sounds useful, I didn't know it existed.
Best Wishes
Phillip
> Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
> ---
> t/t3430-rebase-merges.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/t/t3430-rebase-merges.sh b/t/t3430-rebase-merges.sh
> index 36ca126bcd..e851ede4f9 100755
> --- a/t/t3430-rebase-merges.sh
> +++ b/t/t3430-rebase-merges.sh
> @@ -392,8 +392,8 @@ test_expect_success 'refuse to merge ancestors of HEAD' '
>
> test_expect_success 'root commits' '
> git checkout --orphan unrelated &&
> - (GIT_AUTHOR_NAME="Parsnip" GIT_AUTHOR_EMAIL="root@example.com" \
> - test_commit second-root) &&
> + test_env GIT_AUTHOR_NAME="Parsnip" GIT_AUTHOR_EMAIL="root@example.com" \
> + test_commit second-root &&
> test_commit third-root &&
> cat >script-from-scratch <<-\EOF &&
> pick third-root
next prev parent reply other threads:[~2024-07-22 15:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 6:59 [PATCH 0/4] improve one-shot variable detection with shell function Eric Sunshine
2024-07-22 6:59 ` [PATCH 1/4] t3430: modernize one-shot "VAR=val shell-func" invocation Eric Sunshine
2024-07-22 15:09 ` Phillip Wood [this message]
2024-07-23 9:26 ` Phillip Wood
2024-07-26 6:33 ` Eric Sunshine
2024-07-26 6:15 ` Eric Sunshine
2024-07-22 18:24 ` Junio C Hamano
2024-07-26 6:30 ` Eric Sunshine
2024-07-22 6:59 ` [PATCH 2/4] t4034: fix use of one-shot variable assignment with shell function Eric Sunshine
2024-07-22 6:59 ` [PATCH 3/4] check-non-portable-shell: improve `VAR=val shell-func` detection Eric Sunshine
2024-07-22 14:46 ` Rubén Justo
2024-07-26 6:45 ` Eric Sunshine
2024-07-26 13:15 ` Rubén Justo
2024-07-22 17:26 ` Kyle Lippincott
2024-07-22 18:10 ` Junio C Hamano
2024-07-22 21:35 ` Kyle Lippincott
2024-07-22 21:57 ` Junio C Hamano
2024-07-22 6:59 ` [PATCH 4/4] check-non-portable-shell: suggest alternative for `VAR=val shell-func` Eric Sunshine
2024-07-22 14:47 ` Rubén Justo
2024-07-22 14:50 ` [PATCH 0/4] improve one-shot variable detection with shell function Rubén Justo
2024-07-26 8:15 ` [PATCH v2 0/5] " Eric Sunshine
2024-07-26 8:15 ` [PATCH v2 1/5] t3430: drop unnecessary one-shot "VAR=val shell-func" invocation Eric Sunshine
2024-07-26 18:50 ` Junio C Hamano
2024-07-26 19:32 ` Eric Sunshine
2024-07-26 8:15 ` [PATCH v2 2/5] t4034: fix use of one-shot variable assignment with shell function Eric Sunshine
2024-07-26 8:15 ` [PATCH v2 3/5] check-non-portable-shell: loosen one-shot assignment error message Eric Sunshine
2024-07-26 8:15 ` [PATCH v2 4/5] check-non-portable-shell: suggest alternative for `VAR=val shell-func` Eric Sunshine
2024-07-26 13:11 ` Rubén Justo
2024-07-26 19:31 ` Eric Sunshine
2024-07-26 8:15 ` [PATCH v2 5/5] check-non-portable-shell: improve `VAR=val shell-func` detection Eric Sunshine
2024-07-26 18:38 ` [PATCH v2 0/5] improve one-shot variable detection with shell function Junio C Hamano
2024-07-27 5:35 ` [PATCH v3 " Eric Sunshine
2024-07-27 5:35 ` [PATCH v3 1/5] t3430: drop unnecessary one-shot "VAR=val shell-func" invocation Eric Sunshine
2024-07-27 5:35 ` [PATCH v3 2/5] t4034: fix use of one-shot variable assignment with shell function Eric Sunshine
2024-07-27 5:35 ` [PATCH v3 3/5] check-non-portable-shell: loosen one-shot assignment error message Eric Sunshine
2024-07-27 5:35 ` [PATCH v3 4/5] check-non-portable-shell: suggest alternative for `VAR=val shell-func` Eric Sunshine
2024-07-27 5:35 ` [PATCH v3 5/5] check-non-portable-shell: improve `VAR=val shell-func` detection Eric Sunshine
-- strict thread matches above, loose matches on Subject: below --
2024-10-02 3:39 [PATCH 1/4] t3430: modernize one-shot "VAR=val shell-func" invocation Crystal M Baker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c586f7dc-636b-45a3-acb2-faedfe1068e6@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=ericsunshine@charter.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=rjusto@gmail.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).