diff options
| author | Eric Sunshine <sunshine@sunshineco.com> | 2024-07-27 01:35:08 -0400 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-07-26 22:49:40 -0700 |
| commit | 7bd0cd0e7b29da382fcf2821c1bf087190ab2ffe (patch) | |
| tree | 147590d74706cabacefe9c280cc3d8478d267cfc | |
| parent | a7fa6097473e42b3547cf59fb52fd5ff34e9bd48 (diff) | |
| download | git-7bd0cd0e7b29da382fcf2821c1bf087190ab2ffe.tar.gz | |
check-non-portable-shell: suggest alternative for `VAR=val shell-func`
Most problems reported by check-non-portable-shell are accompanied by
advice suggesting how the test author can repair the problem. For
instance:
error: egrep/fgrep obsolescent (use grep -E/-F)
However, when one-shot variable assignment is detected when calling a
shell function (i.e. `VAR=val shell-func`), the problem is reported, but
no advice is given. The lack of advice is particularly egregious since
neither the problem nor the workaround are likely well-known by
newcomers to the project writing tests for the first time. Address this
shortcoming by recommending the use of `test_env` which is tailor made
for this specific use-case.
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rwxr-xr-x | t/check-non-portable-shell.pl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/t/check-non-portable-shell.pl b/t/check-non-portable-shell.pl index 179efaa39d..903af14294 100755 --- a/t/check-non-portable-shell.pl +++ b/t/check-non-portable-shell.pl @@ -50,7 +50,7 @@ while (<>) { /\blocal\s+[A-Za-z0-9_]*=\$([A-Za-z0-9_{]|[(][^(])/ and err q(quote "$val" in 'local var=$val'); /^\s*([A-Z0-9_]+=(\w*|(["']).*?\3)\s+)+(\w+)/ and exists($func{$4}) and - err '"FOO=bar shell_func" is not portable'; + err '"FOO=bar shell_func" is not portable (use test_env FOO=bar shell_func)'; $line = ''; # this resets our $. for each file close ARGV if eof; |