From: Thor A. <ta...@to...> - 2011-10-17 22:26:27
|
On Mon, Oct 17, 2011 at 04:10:34PM -0600, Jeff Sadowski wrote: > On Mon, Oct 17, 2011 at 4:01 PM, Thor Andreassen <ta...@to...> wrote: > > On Mon, Oct 17, 2011 at 11:56:03AM -0600, Jeff Sadowski wrote: > >> On Mon, Oct 17, 2011 at 10:01 AM, Thor Andreassen <ta...@to...> wrote: > >> > On Mon, Oct 17, 2011 at 08:59:12AM -0600, Jeff Sadowski wrote: > >> >> On Mon, Oct 17, 2011 at 5:43 AM, Thor Andreassen <ta...@to...> wrote: > >> > > >> > [...] > >> > > >> >> > 8<--------8<--------8<--------8<--------8<--------8<-------- > >> >> > for wav in *_L.wav; do > >> >> > sox -M "$wav" "${wav%*_L.wav}_R.wav" "${wav%*_L.wav}_ST.wav" > >> >> > done > >> After thinking about it wouldn't spaces in names break this? > > > > No, this works with spaces because the arguments are quoted. > the for part is where I think the spaces would mess it up getting it > in to the way variable. > doesn't the for delimit by space? Ah I see what you mean, this is not a problem because the asterisk (*) is expanded after word splitting, e.g. see: http://www.gnu.org/software/bash/manual/bashref.html#Filename-Expansion [...] -- best regards Thor Andreassen |