We've already discussed that putting quotes around it won't work due to the IFS definition problem.

Understand?
Gary

At 01:49 PM 4/2/00 -0400, you wrote:
On Sun, 02 Apr 2000, you wrote:
> 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.
>
Put quotes around any filenames with spaces in 'em, i.e.: "This is a Filename
With A Space.txt" rather than This is a Filename With A Space.txt

Understand?
        John


-----------
Nil carborundum illegitimi
http://andysocial.com

Reply via email to