Stewart Stremler wrote:
> begin quoting Stewart Stremler as of Sat, Mar 04, 2006 at 12:12:47PM -0800:
> [snip]
> > The second use of find may be overkill. So long as you don't have any
> > directories with a suffix of .mp3, "mv ${dirname}*.mp3 ${dirname}/"
> > should do the same trick.
>
> ...except that you have files with spaces in 'em. Whoops. Nevermind.
>
> Spaces in filenames are evil.
Artificial limitations are eviler. I will stick with being able to
handle any legal character, this includes backspaces, newlines, and
horizontal tabs in addition to spaces.
What is truly evil is disk-editing a solidus into a filename.
-john
The only reason I can think that a space in a filename would be
considered evil is because the space is a token separator on the shell
command line. Since the original bourne shell had no concept of array
variable, it overloaded the regular scalar variable to be an array
variable by splitting on whitespace by default. To override this, you
had to place the variable inside quotes. Since no one put spaces in
filenames, people got used to thinking that $a was sufficient for
filename use.
This is, what I consider, a poor design initially. However, the mind-set
has stuck, and some modern shells still maintain this broken behaivour
even though they have proper array variables now.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
