> While we already determined that the expression is using the non-portable
> \|, and thus using --posix is allowed to change the behavior, I think we
> have also found an actual bug in sed 4.2.
Not a bug, sed --posix disables \| altogether (and \+, \?, \<, \>,
etc.). Unless you had something dif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 5/27/2009 4:33 AM:
> j...@mocca:~/src/libidn master$ echo 'version 2 '|sed -e 's/version
> \(2\|2\.1\)\([ ,]\)/version 3\2/g'
> version 3
>
> But adding --posix makes it fail:
>
> j...@mocca:~/src/libidn master$ ec
Eric Blake writes:
> According to Simon Josefsson on 5/27/2009 4:33 AM:
>> But adding --posix makes it fail:
>>
>> j...@mocca:~/src/libidn master$ echo 'version 2 '|sed --posix -e 's/version
>> \(2\|2\.1\)\([ ,]\)/version 3\2/g'
>
> You are using \|, which is undefined in BRE, and therefore (c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 5/27/2009 4:33 AM:
> But adding --posix makes it fail:
>
> j...@mocca:~/src/libidn master$ echo 'version 2 '|sed --posix -e 's/version
> \(2\|2\.1\)\([ ,]\)/version 3\2/g'
You are using \|, which is undefined in BRE,
