sed vs gnu sed

[krad]

On 10 November 2011 10:33, Vincent Hoffman <vince at unsane.co.uk> wrote:

> On 10/11/2011 07:00, perryh at pluto.rain.com wrote:
>
>> Vincent Hoffman<vince at unsane.co.uk>  wrote:
>>
>>  bsd sed (correctly according to SUS at least, I believe[1])
>>> appends a newline when writing to standard out, gnu sed doesnt.
>>>
>> The wonderful thing about standards is that there are so many to
>> choose from  -- Tanenbaum
>>
>>  is there any easy way to make our sed do the same as gnu sed here?
>>>
>> As long as it is OK to remove _all_ newlines -- which seems to be
>> the case here -- you could pipe the output through tr -d '\012'
>>
>
>
> Thanks to all for suggestions, I'll move to using tr at some point i think
> but the overhead of any of the approaches is pretty negligable (except for
> firing up python/perl ;)
>
> Vince
>
>
>  ______________________________**_________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<http://lists.freebsd.org/mailman/listinfo/freebsd-questions>
>> To unsubscribe, send any mail to "freebsd-questions-**
>> unsubscribe at freebsd.org <freebsd-questions-unsubscribe at freebsd.org>"
>>
>
> ______________________________**_________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<http://lists.freebsd.org/mailman/listinfo/freebsd-questions>
> To unsubscribe, send any mail to "freebsd-questions-**
> unsubscribe at freebsd.org <freebsd-questions-unsubscribe at freebsd.org>"
>


you could sidestep the issue entirely /usr/ports/textproc/gsed