Date: Thu, 13 Jan 2011 09:47:38 +0100 From: Oliver Pinter <oliver.pntr@gmail.com> To: Peter Jeremy <peterjeremy@acm.org> Cc: stable@freebsd.org Subject: Re: sed is broken under freebsd? Message-ID: <AANLkTimzFcrFFT2BC0JnN=zG3TAzgJ9eXhGKhGPFCnhD@mail.gmail.com> In-Reply-To: <20110112195746.GA16732@server.vk2pj.dyndns.org> References: <AANLkTin=Jeah8UX7QB-Uk1x9VYBtnFw=nX8fptLJW%2Bs4@mail.gmail.com> <20110112195746.GA16732@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
yeah, and the solution is was Clifton wrote, but double escaped new-line in tcsh On 1/12/11, Peter Jeremy <peterjeremy@acm.org> wrote: > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimzFcrFFT2BC0JnN=zG3TAzgJ9eXhGKhGPFCnhD>