From owner-freebsd-questions@FreeBSD.ORG Thu Nov 10 10:51:45 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5ECE9106566C for ; Thu, 10 Nov 2011 10:51:45 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (www.unsane.co.uk [85.233.185.162]) by mx1.freebsd.org (Postfix) with ESMTP id E2BA48FC13 for ; Thu, 10 Nov 2011 10:51:43 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id pAAAXD8i037695 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 10 Nov 2011 10:33:13 GMT (envelope-from vince@unsane.co.uk) Message-ID: <4EBBA868.5030000@unsane.co.uk> Date: Thu, 10 Nov 2011 10:33:12 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4EBA5646.5030102@unsane.co.uk> <4ebb7681.kE6yc4aqdzf2C9LV%perryh@pluto.rain.com> In-Reply-To: <4ebb7681.kE6yc4aqdzf2C9LV%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: sed vs gnu sed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2011 10:51:45 -0000 On 10/11/2011 07:00, perryh@pluto.rain.com wrote: > Vincent Hoffman 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"