Benjamin Scott <[EMAIL PROTECTED]> writes:
>On Mon, 18 Jun 2001, Tom Rauschenbach wrote:
>> Oooh. I HATE spaces in file names. The file system may support it, but
>> they break almost every script.
>
>They shouldn't break a well-written script. There are, alas, a
>large number of poorly written scripts. (Something I've as guilty of
>as the next guy, I'm sure.)
I would appreciate some pointers on this. For example, I often use
this idiom:
for x in *.txt; do sed 's/which/that/' $x >foo && mv foo $x; done
Which would of course break if any filename had spaces.
I know about the -exec and -print0 options of find, but AFAIK -exec
only works with a single command and -print0 only works with a few
programs that can accept null-delimited filenames. Do you have
something else in mind?
- Jim Van Zandt
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
