That's because the "for ... in ...; do ...; done" command interprets any
white space as separators - and, I think, without respect for quoting, or
backslash-escaping.
So how do you get around it? I am out of ideas. I am simply resigned to
never using a filename with a space in it - which is difficult to do when
you work with Windows often. I myself keep spaces away, but anytime I get
a file from another Windows user, I try to rename it, usually converting
spaces to underscores.
It's a pain in the ass, but I don't know of any better way to handle
it. I can't find anything in the bash about changing whitespace
definition (*perhaps* $IFS ???). I just don't know. I'll play with it,
and if I find anything, I'll post.
-Matt Stegman
<[EMAIL PROTECTED]>
On Sat, 1 Apr 2000, Gary Bunker wrote:
> OK, that was a brainiac move on my part. Didn't realize the importance
> of the apostrophe direction in your post. HOWEVER, upon doing it
> correctly, I end up with a different problem. If the files listed in
> the M3U playlist include spaces, it chokes. Without spaces, no
> problem. So, still no elegant solution.
>
> On 1 Apr, Axalon Bloodstone wrote:
> >
> > That means your useing the wrong ` make sure it's ` not ' or it will not
> > work. also if it's not in the current dir you'll need to give the path
> > like
> >
> > for i in `cat /mnt/mp3/playlist.m3u`
>
> --
>
> -----------
> Nil Carborundum Illegitimi
> http://andysocial.com
>
