GNU bug report logs - #30794
Cannot produce backslash through hexadecimal - sed (GNU sed) 4.2.2

Previous Next

Package: sed;

Reported by: 0xddaa <at> gmail.com

Date: Tue, 13 Mar 2018 15:26:01 UTC

Severity: normal

Done: Jim Meyering <jim <at> meyering.net>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 30794 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: 0xddaa <0xddaa <at> gmail.com>, 30794 <at> debbugs.gnu.org
Subject: Re: bug#30794: Cannot produce backslash through hexadecimal - sed
 (GNU sed) 4.2.2
Date: Wed, 14 Mar 2018 16:43:11 -0600
[Message part 1 (text/plain, inline)]
Replying to myself:

On Wed, Mar 14, 2018 at 04:34:18PM -0600, Assaf Gordon wrote:
> > [...]
> > sed-1.18 : x5c1
> > sed-2.05 : x5c1
> > sed-3.01 : x5c1
> > sed-3.02 : x5c1
> > [...]
 
I checked the NEWS file,
and found that backslash sequences (e.g. \n \t \xNN \dNNN \oNNN)
were added in version 3.02.80 (which I don't think is common and
we don't have the source code).

I changed the NEWS accordingly (attached updated patch).

OK to push?

thanks,
 - assaf

[0001-sed-treat-x5c-as-literal-backslash.patch (text/x-diff, attachment)]

This bug report was last modified 7 years and 131 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.