Thanks Re: OT: help with mawk

2004-03-20 Thread ghcbc
On Sat, Mar 20, 2004 at 02:14:25AM +, Clive Standbridge wrote: > On Thu 18 Mar 2004 16:53:58 +(-0800), [EMAIL PROTECTED] wrote: > > On Thu, Mar 18, 2004 at 06:19:43PM +0100, Joachim Fahnenmueller wrote: > > > Hi ghcbc, > > > > > > VARIABLENAME=$(mawk 'whatever') . > > > > Hi, > > > > Tha

Re: OT: help with mawk

2004-03-19 Thread Clive Standbridge
On Thu 18 Mar 2004 16:53:58 +(-0800), [EMAIL PROTECTED] wrote: > On Thu, Mar 18, 2004 at 06:19:43PM +0100, Joachim Fahnenmueller wrote: > > Hi ghcbc, > > > > VARIABLENAME=$(mawk 'whatever') . > > Hi, > > Thanks. I can get this to work on the command line, but not in a bash > script. I thin

Re: OT: help with mawk

2004-03-18 Thread gcrimp
On Thu, Mar 18, 2004 at 06:19:43PM +0100, Joachim Fahnenmueller wrote: > Hi ghcbc, > > VARIABLENAME=$(mawk 'whatever') . Hi, Thanks. I can get this to work on the command line, but not in a bash script. bash$ Myvar=$(mawk 'gsub("/","") { print }') The shell will then wait for input. I type s

Re: OT: help with mawk

2004-03-18 Thread Joachim Fahnenmueller
Hi ghcbc, VARIABLENAME=$(mawk 'whatever') . BTW: Your syntax seems strange to me. AFAIK it should be something like mawk '/pattern/ {action}' (see man mawk). On Wed, Mar 17, 2004 at 07:19:27PM -0800, [EMAIL PROTECTED] wrote: > Hi, > > I am writing a shell script to process a dir tree looking fo