From: Ben Walton <bdwalton@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] Change sed i\ usage to something Solaris' sed can handle
Date: Mon, 28 Oct 2013 21:10:46 +0000 [thread overview]
Message-ID: <CAP30j15+E4cz_kwJwaSH7-3agwC5J3jGNfaixSUg2=8xAzZoQg@mail.gmail.com> (raw)
In-Reply-To: <877gcx1eho.fsf@igel.home>
On Mon, Oct 28, 2013 at 5:39 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Ben Walton <bdwalton@gmail.com> writes:
>
>> diff --git a/t/t4015-diff-whitespace.sh b/t/t4015-diff-whitespace.sh
>> index 3fb4b97..0126154 100755
>> --- a/t/t4015-diff-whitespace.sh
>> +++ b/t/t4015-diff-whitespace.sh
>> @@ -145,7 +145,8 @@ test_expect_success 'another test, with --ignore-space-at-eol' 'test_cmp expect
>> test_expect_success 'ignore-blank-lines: only new lines' '
>> test_seq 5 >x &&
>> git update-index x &&
>> - test_seq 5 | sed "/3/i \\
>> + test_seq 5 | sed "/3/i\\
>> +\
>> " >x &&
>
> Why do you need the \<nl>? Since it is inside double quotes the shell
> will remove it during expansion.
It's an escape. Without it, sed throws:
sed: -e expression #1, char 5: expected \ after `a', `c' or `i'
Thanks
-Ben
--
---------------------------------------------------------------------------------------------------------------------------
Take the risk of thinking for yourself. Much more happiness,
truth, beauty and wisdom will come to you that way.
-Christopher Hitchens
---------------------------------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2013-10-28 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 21:26 [PATCH] Change sed i\ usage to something Solaris' sed can handle Ben Walton
2013-10-28 17:39 ` Andreas Schwab
2013-10-28 21:10 ` Ben Walton [this message]
2013-10-28 21:59 ` Andreas Schwab
2013-10-30 19:30 ` Junio C Hamano
2013-11-03 13:08 ` Ben Walton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP30j15+E4cz_kwJwaSH7-3agwC5J3jGNfaixSUg2=8xAzZoQg@mail.gmail.com' \
--to=bdwalton@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).