Re: [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character
From: Miklos Vajna <hidden>
Date: 2016-06-15 22:49:06
Possibly related (same subject, not in this thread)
- 2016-06-15 · [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character · Miklos Vajna <hidden>
- 2016-06-15 · Re: [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character · Miklos Vajna <hidden>
- 2016-06-15 · Re: [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character · Santi Béjar <hidden>
- 2016-06-15 · Re: [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character · Miklos Vajna <hidden>
On Wed, Jul 07, 2010 at 05:29:29PM -0700, Junio C Hamano [off-list ref] wrote:
Our patches do seem to fix the reading side of the issue, but I am not sure if the writing side needs further fix. If I recall, the script had liberal use of "echo $var"; some implementations of echo interprets backslash sequence without being asked with an explicit "-e".
Possibly, I just have the bash builtin and the coreutils echo here, both are writing \t properly without -e.
Attachments
- (unnamed) [application/pgp-signature] 198 bytes