From owner-freebsd-questions@FreeBSD.ORG Sun Feb 1 10:58:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B573816A4CE for ; Sun, 1 Feb 2004 10:58:25 -0800 (PST) Received: from lilzmailso02.liwest.at (lilzmailso02.liwest.at [212.33.55.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AB6943D1D for ; Sun, 1 Feb 2004 10:58:24 -0800 (PST) (envelope-from dgw@liwest.at) Received: from cm58-27.liwest.at ([212.33.58.27]) by lilzmailso02.liwest.at with esmtp (Exim 4.24) id 1AnMnW-00041I-0i; Sun, 01 Feb 2004 19:58:22 +0100 From: Daniela To: Chris Pressey Date: Sun, 1 Feb 2004 19:52:42 +0000 User-Agent: KMail/1.5.3 References: <200402010138.44102.dgw@liwest.at> <200402011533.58877.dgw@liwest.at> <20040201101027.2b90499d.cpressey@catseye.mine.nu> In-Reply-To: <20040201101027.2b90499d.cpressey@catseye.mine.nu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402011952.42130.dgw@liwest.at> cc: questions@freebsd.org Subject: Re: OT: sed problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 18:58:25 -0000 On Sunday 01 February 2004 18:10, Chris Pressey wrote: > On Sun, 1 Feb 2004 15:33:58 +0000 > > Daniela wrote: > > On Sunday 01 February 2004 01:34, Jez Hancock wrote: > > > On Sun, Feb 01, 2004 at 01:38:44AM +0000, Daniela wrote: > > > > I was wondering how I can do the following with sed (or another > > > > program): 1. Output only the text from the start of the line to > > > > the first pipe character 2. Output only the text between the last > > > > and the previous pipe character Or, split the line at the pipe > > > > characters and assign the parts to different shell variables. > > > > > > #!/bin/sh > > > test="one|two|three" > > > set `echo "$test" | sed -e 's/\|/ /g'` > > > > > > # $1="one", $2="two", $3="three": > > > echo $@ > > > > This doesn't work when the parts between the pipe characters contain > > spaces themselves. > > Nor does the awk approach I posted, incidentally - the problem being > that sh likes to split up its input into variables, by spaces. awk -F'|' '{ print $1 }' does work indeed. This way, I can assign the parts to different variables, and dismiss the parts I don't need. > You can work around it by translating the spaces into some unused > character first, then translating pipes to spaces, then finally > translating the unused characters back into spaces in each of the > variables. > > There may be a simpler way, but if so, I don't know what it is. > > Or you could avoid sh variables and do whatever processing you have to > do entirely in awk (or perl.) I really like csh programming. Everyone says that csh is crap for scripting, but it isn't. I think Perl is harder than csh. But let's not start another holy war.