summaryrefslogtreecommitdiff
path: root/t/lib-bash.sh
diff options
context:
space:
mode:
authorLibravatar Eric Sunshine <sunshine@sunshineco.com>2018-08-13 04:47:37 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-08-13 12:22:12 -0700
commitd93871143fdb7c11ddea81aa7f698e5eee0246e5 (patch)
tree1f773aa5dbcb210176a75483e6594d76e84bb09f /t/lib-bash.sh
parentchainlint: recognize multi-line $(...) when command cuddled with "$(" (diff)
downloadtgif-d93871143fdb7c11ddea81aa7f698e5eee0246e5.tar.xz
chainlint: let here-doc and multi-line string commence on same line
After swallowing a here-doc, chainlint.sed assumes that no other processing needs to be done on the line aside from checking for &&-chain breakage; likewise, after folding a multi-line quoted string. However, it's conceivable (even if unlikely in practice) that both a here-doc and a multi-line quoted string might commence on the same line: cat <<\EOF && echo "foo bar" data EOF Support this case by sending the line (after swallowing and folding) through the normal processing sequence rather than jumping directly to the check for broken &&-chain. This change also allows other somewhat pathological cases to be handled, such as closing a subshell on the same line starting a here-doc: ( cat <<-\INPUT) data INPUT or, for instance, opening a multi-line $(...) expression on the same line starting a here-doc: x=$(cat <<-\END && data END echo "x") among others. Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/lib-bash.sh')
0 files changed, 0 insertions, 0 deletions