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

Previous Next

Full log

View this message in rfc822 format

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: bug#30794: Cannot produce backslash through hexadecimal - sed (GNU sed) 4.2.2
Date: Wed, 14 Mar 2018 16:34:18 -0600

Hello Jim,

On Tue, Mar 13, 2018 at 09:45:55PM -0700, Jim Meyering wrote:
> On Tue, Mar 13, 2018 at 7:45 PM, Assaf Gordon <assafgordon <at> gmail.com> wrote:
> ...
> > I expanded your fix by adding tests and news item, see attached patch.
> >
> Thanks for the fine work from both of you.
> Assaf, I think it's fair to extend the bound in the NEWS to say this:
> 
>   [Bug present since the beginning]
> 
> To conclude that, I ran the following on a modern system for which I
> have built many old sed binaries.
> [...]
> $ for i in $(env ls -dv /p/p/sed-*); do printf '%-14s: ' $i; echo z |
> $i/bin/sed 's/\(z\)/\x5c1/'; done|sed s/.....//    s:
> sed-1.18 : x5c1
> sed-2.05 : x5c1
> sed-3.01 : x5c1
> sed-3.02 : x5c1
> [...]

Sorry for bike-shedding,
but wouldn't you say that if "\x5c1" is printed it means that older seds
do not understand hex characters, and simply treated "\x" as "x" ?

-assaf

Previous Next

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