[Bug 14541] sed: s-command with "semi-special" delimiters get wrong behaviour

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=14541

Christoph Anton Mitterer <calestyo at scientia.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #3 from Christoph Anton Mitterer <calestyo at scientia.org> ---
I just went through my list of test cases in
https://www.austingroupbugs.net/view.php?id=1551#c5612 :


It seems busybox now (with the patch) behaves as GNU, except or one case:

GNU:
$ printf '%s\n' 'oxo' | sed 's1\(x\)1\11'
o1o
$ printf '%s\n' 'owo' | sed 's1\(x\)1\11'
owo


BusyBox with patch:
$ printf '%s\n' 'oxo' | ./busybox sed 's1\(x\)1\11'
oxo
$ printf '%s\n' 'owo' | ./busybox sed 's1\(x\)1\11'
owo


So in the replacement, the bug doesn't seem to be fixed, yet.

Same case,.. the \1 is first "un-delimitered" but then still counted as \1,
though the \ should have already been removed because of the "un-delimitering".

Thus reopneing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.