Date: Fri, 14 Oct 2016 09:30:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213474] sed behaviuor with a/i/c operands. Message-ID: <bug-213474-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213474 Bug ID: 213474 Summary: sed behaviuor with a/i/c operands. Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: kpect@protonmail.com Hello. Al of a sudden sed began to act differently on FreeBSD 11=20 On FreeBSD 11.0 following script (<------> - tab character) # cat file SEARCHED_LINE #!/bin/sh sed -E -i '.orig' \ <------>-e '/^SEARCHED_LINE/ a\ <------>line1\ line2\ <------>\<------>line3' \ file performs this output: SEARCHED_LINE <------>line1 line2 <------><------>line3 While on FreeBSD 10.3 and previuos versions it performed this: line1 line2 <------>line3 Why have you changed pretty sane and convenient sed's behaviuor to gsed's o= ne? My scripts looked very neat and structured with previuos BSD sed. Do I have to rewrite all my scripts now? Regards, Sergey. --=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>