From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Sat, 26 May 2007 07:38:55 GMT
Subject: Re: Bug: git-rebase goofs up \n in commit messages
Message-ID: <20070526073855.GA6395@gondor.apana.org.au>
In-Reply-To: <20070526062748.GA21229@coredump.intra.peff.net>

On Sat, May 26, 2007 at 02:27:48AM -0400, Jeff King wrote:
> 
> No, I meant would the shell, while interpolating a double-quoted string
> "\n", always preserve the string and pass the backslash and 'n' to
> printf?  Clearly \\ and \" get interpolated, but I don't know the rules
> for "unrecognized" backslash sequences.

Yep.  Section 2.2.3 says that the backslash within double quotes will
only serve as an escape character for $, `, ", \ and <newline>.  Of
course, you can always use a single quote instead, i.e.,

printf '%s\n' "$VAR"

Then there can be no doubt :)

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt