Date: Thu, 10 Nov 2011 10:33:12 +0000 From: Vincent Hoffman <vince@unsane.co.uk> To: freebsd-questions@freebsd.org Subject: Re: sed vs gnu sed Message-ID: <4EBBA868.5030000@unsane.co.uk> In-Reply-To: <4ebb7681.kE6yc4aqdzf2C9LV%perryh@pluto.rain.com> References: <4EBA5646.5030102@unsane.co.uk> <4ebb7681.kE6yc4aqdzf2C9LV%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/11/2011 07:00, perryh@pluto.rain.com wrote: > Vincent Hoffman<vince@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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EBBA868.5030000>