From owner-freebsd-questions@FreeBSD.ORG Thu Nov 10 00:52:20 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 B65B6106564A for ; Thu, 10 Nov 2011 00:52:20 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 968278FC0A for ; Thu, 10 Nov 2011 00:52:20 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id pAA0FVbE091838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Nov 2011 16:15:34 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id pAA0FVLa091837; Wed, 9 Nov 2011 16:15:31 -0800 (PST) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA10921; Wed, 9 Nov 11 16:00:24 PST Date: Wed, 09 Nov 2011 23:00:17 -0800 From: perryh@pluto.rain.com To: vince@unsane.co.uk Message-Id: <4ebb7681.kE6yc4aqdzf2C9LV%perryh@pluto.rain.com> References: <4EBA5646.5030102@unsane.co.uk> In-Reply-To: <4EBA5646.5030102@unsane.co.uk> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD-Questions@freebsd.org 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 00:52:20 -0000 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'