GNU bug report logs - #34316
sed misbehavior on BRE's

Previous Next

Package: sed;

Reported by: "Lange, Markus" <M.Lange <at> dnb.de>

Date: Mon, 4 Feb 2019 15:35:06 UTC

Severity: normal

Tags: moreinfo, notabug

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: "Lange, Markus" <M.Lange <at> dnb.de>,
 "34316 <at> debbugs.gnu.org" <34316 <at> debbugs.gnu.org>
Subject: Re: bug#34316: sed misbehavior on BRE's
Date: Wed, 13 Feb 2019 16:15:08 -0700
tags 34316 notabug
close 34316
stop

Hello,

On 2019-02-11 12:45 a.m., Lange, Markus wrote:
> # sed --version
> sed (GNU sed) 4.7
> ...
> 
> Using LANG=C (LC_* unset) works as expected:
> # LANG=C sed -n 's/^.*004K...\([0-
> 9xX]\{13\}\).*006V...\(.\{1,32\}\).*\(.020F.*\)021A.*$/\2 \1\3/p'
> Fehlerpica.dat
> 138742c156c1445f8bdc3a7845548c00 9783507435339020F a19.04.03
> 18290030a02544e6a451538b0e44f9e2 9783507435377020F a19.04.03
> 4c7ff6d790b34470852434f5ee41200b 9783034312189020F a12.12.11
> 
> Using LANG=en_us.utf8 don't get results.
> 

Thanks for confirming.

Since the file contains binary bytes, they would not match as valid
characters under UTF8 locale.

Using LC_ALL=C is indeed the solution.

As such, I'm closing this as "not a bug" but discussion can
continue by replying to this thread.

-assaf






This bug report was last modified 6 years and 158 days ago.

Previous Next


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