]> git.ipfire.org Git - thirdparty/git.git/commit - t/chainlint/block.expect
chainlint.sed: improve ?!AMP?! placement accuracy
authorEric Sunshine <sunshine@sunshineco.com>
Mon, 13 Dec 2021 06:30:50 +0000 (01:30 -0500)
committerJunio C Hamano <gitster@pobox.com>
Mon, 13 Dec 2021 22:15:29 +0000 (14:15 -0800)
commitdb8c7a1cc02e545dd75b55e2ccbab2de51cd06ae
treeacffc94f666354a3b6c21b80621dc54495317f30
parentf30c1d5eb1ceeec460ea4cd2089ece63156f5eb0
chainlint.sed: improve ?!AMP?! placement accuracy

When chainlint.sed detects a broken &&-chain, it places an ?!AMP?!
annotation at the beginning of the line. However, this is an unusual
location for programmers accustomed to error messages (from compilers,
for instance) indicating the exact point of the problem. Therefore,
relocate the ?!AMP?! annotation to the end of the line in order to
better direct the programmer's attention to the source of the problem.

Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
23 files changed:
t/chainlint.sed
t/chainlint/arithmetic-expansion.expect
t/chainlint/block.expect
t/chainlint/broken-chain.expect
t/chainlint/case.expect
t/chainlint/command-substitution.expect
t/chainlint/cuddled.expect
t/chainlint/for-loop.expect
t/chainlint/here-doc-multi-line-command-subst.expect
t/chainlint/here-doc-multi-line-string.expect
t/chainlint/if-in-loop.expect
t/chainlint/if-then-else.expect
t/chainlint/inline-comment.expect
t/chainlint/loop-in-if.expect
t/chainlint/multi-line-string.expect
t/chainlint/nested-cuddled-subshell.expect
t/chainlint/nested-here-doc.expect
t/chainlint/nested-subshell-comment.expect
t/chainlint/pipe.expect
t/chainlint/semicolon.expect
t/chainlint/subshell-here-doc.expect
t/chainlint/subshell-one-liner.expect
t/chainlint/while-loop.expect