Date: Thu, 20 Oct 2016 16:35:42 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213474] sed behavior change with a/i/c operands. Message-ID: <bug-213474-8-HuhU2S7tEA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213474-8@https.bugs.freebsd.org/bugzilla/> References: <bug-213474-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213474 Pedro F. Giffuni <pfg@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #175892|0 |1 is obsolete| | --- Comment #3 from Pedro F. Giffuni <pfg@FreeBSD.org> --- Created attachment 175985 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175985&action= =3Dedit Add a CFLAG to re-enable FreeBSD 10 behavior The new behavior in FBSD 11+, is also present in SYSV UNIX. The new behavior should help people migrating from Solaris as well as linux so I think it sh= ould be the default. It still looks convenient and easy to add a CFLAG (LEGACY_BSDSED_COMPAT) to make it easier to re-enable the old behavior. I am not convinced we should go as far as adding a new build option for thi= s, but at least this should make it easier to custom-build a sed that supports= the old behavior. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213474-8-HuhU2S7tEA>