[Bug 14541] sed: s-command with "semi-special" delimiters get wrong behaviour
bugzilla at busybox.net
bugzilla at busybox.net
Tue Feb 1 20:16:08 UTC 2022
https://bugs.busybox.net/show_bug.cgi?id=14541
Christoph Anton Mitterer <calestyo at scientia.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REOPENED |RESOLVED
--- Comment #4 from Christoph Anton Mitterer <calestyo at scientia.org> ---
I hadn't seen the 2nd commit, f12fb1e4092900f26f7f8c71cde44b1cd7d26439, when
testing.
That also fixes the case from comment #3.
Now, BusyBox sed seems to behave identically to GNU sed in all the cases I had
given in:
https://www.austingroupbugs.net/view.php?id=1551#c5612
Especially, it also seems to consider "un-delimitered" delimiters that are also
special characters as "still special" (or at least I tried that with '.') -
which is, while IMO not clearly defined by POSIX, identical to the behaviour of
GNU sed, see https://www.austingroupbugs.net/view.php?id=1551#c5648 for test
cases.)
Thus closing again.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list