mirror of
https://github.com/git/git.git
synced 2026-01-11 21:33:13 +09:00
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>
This commit is contained in:
parent
a7fa609747
commit
7bd0cd0e7b
@ -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;
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user