[Bug 271817] sed: range change with N results in no output

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271817

--- Comment #16 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=a2d78713171cf138b5ae50d61f82df1af7574c95

commit a2d78713171cf138b5ae50d61f82df1af7574c95
Author:     Valeriy Ushakov <uwe@netbsd.org>
AuthorDate: 2024-12-17 22:27:01 +0000
Commit:     Warner Losh <imp@FreeBSD.org>
CommitDate: 2024-12-17 22:34:06 +0000

    sed: The change ("c") command should start a new cycle.

    The "c" command should start the next cycle as clarified in POSIX 2024.
    This is also consistent with historical and gnu sed behavior.

    This patch is from OpenBSD by way of NetBSD with a tweak to the man page
    date by me.

    Confirmed the test case in the bug now works.

    PR:             271817
    Obtained from:  NetBSD (1.39 uwe), OpenBSD (1.39 millert)
    Sponsored by:   Netflix

 usr.bin/sed/process.c | 2 +-
 usr.bin/sed/sed.1     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.