sed is broken under freebsd?
oliver.pntr at gmail.com
Thu Jan 13 08:47:39 UTC 2011
yeah, and the solution is was Clifton wrote, but double escaped new-line in tcsh
On 1/12/11, Peter Jeremy <peterjeremy at acm.org> wrote:
> On 2011-Jan-12 02:32:52 +0100, Oliver Pinter <oliver.pntr at 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
More information about the freebsd-stable