Preserving Blanks in Parameters to Shell Script

Preserving Blanks in Parameters to Shell Script

Aharon Schkolnik aschkolnik at gmail.com
Mon Jun 14 16:14:55 IDT 2010


On Monday, June 14, 2010, Noam Meltzer wrote:
> I'm sorry. I tend to forget why I hate shell scripts.
> Use "$@" instead. (checked it this time, it works ;-) )

Yep - looks like nice ffmpeg "$@" does the trick.

Thanks !



> 
> 2010/6/14 Aharon Schkolnik <aschkolnik at gmail.com>
> 
> > On Monday, June 14, 2010, Noam Meltzer wrote:
> > > use $@ instead of $*
> > 
> > Does that work for you ?
> > 
> > I still get the same results - the script treates file\ one as two
> > parameters - file and one.
> > 
> > > On Mon, Jun 14, 2010 at 3:27 PM, Aharon Schkolnik
> > 
> > <aschkolnik at gmail.com>wrote:
> > > > Hi.
> > > > 
> > > > I want to write a script which will nice ffmpeg whatever
> > > > parameters it is given - ie:
> > > > 
> > > > #!/bin/sh
> > > > 
> > > > nice ffmpeg $*
> > > > 
> > > > #
> > > > 
> > > > 
> > > > However, what if I have a file named `file one'
> > > > 
> > > > 
> > > > I would like to type `myscript -i file\ one output.whatever`
> > > > 
> > > > I do not want to change what I type - the script needs to be a
> > > > drop-in replacement for the ffmpeg command.
> > > > 
> > > > 
> > > > Is there any way to do make the script preserve the backslashed
> > > > space ?
> > > > 
> > > > TIA

-- 
  The day is short, and the work is great,    |  Aharon Schkolnik
  and the laborers are lazy, and the reward   |  
  is great, and the Master of the house is    |  aschkolnik at gmail.com
  impatient. - Ethics Of The Fathers Ch. 2    |  054 3344135



More information about the Linux-il mailing list