Re: POSIX woes in t7810.87: dash bash or bash dash?
From: Jeff King <hidden>
Date: 2016-06-15 22:51:30
Possibly related (same subject, not in this thread)
- 2016-06-15 · POSIX woes in t7810.87: dash bash or bash dash? · Michael J Gruber <hidden>
- 2016-06-15 · Re: POSIX woes in t7810.87: dash bash or bash dash? · Jonathan Nieder <hidden>
- 2016-06-15 · Re: POSIX woes in t7810.87: dash bash or bash dash? · Jeff King <hidden>
- 2016-06-15 · Re: POSIX woes in t7810.87: dash bash or bash dash? · Junio C Hamano <hidden>
- 2016-06-15 · Re: POSIX woes in t7810.87: dash bash or bash dash? · Jeff King <hidden>
On Mon, Jun 20, 2011 at 02:46:08PM -0700, Junio C Hamano wrote:
quoted hunk ↗ jump to hunk
diff --git a/t/t7810-grep.sh b/t/t7810-grep.sh index 69bd576..6379ad6 100755 --- a/t/t7810-grep.sh +++ b/t/t7810-grep.sh@@ -658,9 +658,9 @@ test_expect_success LIBPCRE 'grep -P -v pattern' ' ' test_expect_success LIBPCRE 'grep -P -i pattern' ' - { - echo "hello.c: printf(\"Hello world.\n\");" - } >expected && + cat >expected <<-EOF && + hello.c: printf("Hello world.\n"); + EOF
Do you need to quote EOF to suppress expansion in the here document? Both bash and dash seem to pass unknown backslash-escapes like "\n" through unharmed, but I don't know if that is portable (they do both munge known escapes like "\\", of course). -Peff