Oğuz wrote, on 25 Mar 2020:
>
> echo n | sed '\n\nnd'
>
> Above command returns 'n' with GNU sed, and nothing with BSD seds and
> OmniOS sed. The standard says
>
>
>-
>
>In a context address, the construction "\cBREc", where *c* is any
>character other than or , shall be ident
> Given that implementations differ, we should probably make the
> behaviour explicitly unspecified.
But this might be a bug in GNU's implementation.
$ echo t | sed 'st\ttt' | xxd
: 0a .
$
$ echo n | sed 'sn\nnn' | xxd
: 6e
Oğuz wrote, on 26 Mar 2020:
>
> > Given that implementations differ, we should probably make the
> > behaviour explicitly unspecified.
>
> But this might be a bug in GNU's implementation.
>
[...]
>
> Personally, I think BSD sed's behavior should be standardized and GNU
> would not object to tha
O?uz wrote:
> > Given that implementations differ, we should probably make the
> > behaviour explicitly unspecified.
>
> But this might be a bug in GNU's implementation.
Why should a behavior that is aligned with the classical UNIX behavior
(Solaris) be buggy?
Jörg
--
EMail:jo...@schily.net
Geoff Clare wrote:
> Solaris and HP-UX output "n" the same as GNU sed.
Sou you verified what I assumed from the fact that Solaris, AIX and HP-UX are
based on a common source from the i18n project.
Jörg
--
EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin
joe
26 Mart 2020 Perşembe tarihinde Joerg Schilling <
joerg.schill...@fokus.fraunhofer.de> yazdı:
> O?uz wrote:
>
> > > Given that implementations differ, we should probably make the
> > > behaviour explicitly unspecified.
> >
> > But this might be a bug in GNU's implementation.
>
> Why should a beha
Sorry, I was confusing the 'd' command, thinking 'display', for the 'l'
command. Since stdout is supposed to echo after processing, I did have it
reversed; if the gnu version echos the 'n' it probably wasn't 'delete'd, and
for the others it likely was.
On Wednesday, March 25, 2020 Harald van D
Date:Thu, 26 Mar 2020 09:11:16 +
From:Geoff Clare
Message-ID: <20200326091116.GB22632@lt2.masqnet>
| Given that implementations differ, we should probably make the
| behaviour explicitly unspecified.
I'd agree with that - it isn't as though it really matters
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1318
==
Reported By:nate_karstens
Assigned To:
