Date: Wed, 12 Jan 2011 21:10:21 -0800 (PST) From: "Chris H" <chris#@1command.com> To: freebsd-stable@freebsd.org Cc: cliftonr@lava.net Subject: Re: sed is broken under freebsd? Message-ID: <a3ab8ba12e7c03cac40bc4baf1829f90.HRCIM@webmail.1command.com> In-Reply-To: <20110112223229.GB65854@rancor.immure.com> References: <AANLkTin=Jeah8UX7QB-Uk1x9VYBtnFw=nX8fptLJW%2Bs4@mail.gmail.com> <20110112070009.GB20924@lava.net> <20110112223229.GB65854@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, January 12, 2011 2:32 pm, Bob Willcox wrote: > On Tue, Jan 11, 2011 at 09:00:09PM -1000, Clifton Royston wrote: > >> On Wed, Jan 12, 2011 at 02:32:52AM +0100, Oliver Pinter wrote: >> >>> hi all! >>> >>> The freebsd versions of sed contained a bug/regression, when \n char >>> can i subsitue, gsed not affected with this bug: >> >>> FreeBSD xxx 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 >>> UTC 2010 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC >>> i386 aa@xxx ~> echo axa | sed s/x/\n/g ana aa@xxx ~> echo axa | sed s/x/'\n'/g >>> ana >> >> Different than GNU is not a bug. >> >> >> I have 7.3 here. It behaves as the above, which is how the man page says it >> should work. The following is how the man page specifies you can substitute a >> newline, by prefacing a quoted actual newline with a backslash: >> >> $ echo axa | sed 's/x/\ >> >>> /g' >>> >> a a >> >> That's how I remember classic sed behaving (Unix v7 or thereabouts.) >> -- Clifton >> > > FWI, AIX 6.1 sed works as the FreeBSD sed does. FWIW On a hunch, I just performed an experimentwith sed(1) against gsed on 50,000 html documents. My mission; to replace all instances of: <HTML> <HEAD> with: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" dir="ltr"> in an effort to see how long it would take to perform the operation for each of the two versions. The results? sed(1) (as provided by the BSD family of operating systems): ~2 seconds gsed: ~4.5 seconds Apologies for the extra noise on the list, but I do a tremendous amount of editing with sed(1) on almost a daily basis. It's a _fantastic_ tool, that saves me _zillions_ of hours. So I'm afraid I become a bit defensive when hearing anyone defame it - it's been like a trusted friend to me. :) --Chris > > > -- > Bob Willcox When the ax entered the forest, the trees said, > bob@immure.com "The handle is one of us!" Austin, TX > -- Turkish proverb > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a3ab8ba12e7c03cac40bc4baf1829f90.HRCIM>