Date: Thu, 13 Jan 2011 06:57:46 +1100 From: Peter Jeremy <peterjeremy@acm.org> To: Oliver Pinter <oliver.pntr@gmail.com> Cc: stable@freebsd.org Subject: Re: sed is broken under freebsd? Message-ID: <20110112195746.GA16732@server.vk2pj.dyndns.org> In-Reply-To: <AANLkTin=Jeah8UX7QB-Uk1x9VYBtnFw=nX8fptLJW%2Bs4@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 2011-Jan-12 02:32:52 +0100, Oliver Pinter <oliver.pntr@gmail.com> wrote: >The freebsd versions of sed contained a bug/regression, when \n char >can i subsitue, gsed not affected with this bug: gsed contains non-standard extensions and you have been suckered into using them. Try using 'gsed --posix' and/or setting POSIXLY_CORRECT. This is part of the GNU/FSF "lockin" policy that encourages people to use their non-standard extensions to ensure that you don't have any choice other than to use their software. -- Peter Jeremy [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAk0uB7oACgkQ/opHv/APuIeeogCgi6x/JlUXXRObGwEkZNBIPim5 CJcAnjidhge2xSdA4yLiV8kyX7JMtY66 =JHLf -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110112195746.GA16732>