Craig Dickson wrote: > > Dimitri Maziuk wrote: > > > Wrong. There's a reason why people with half a clue don't put > > spaces in paths, and inadequacy of tools is not it. Unless your > > computer can read minds, it has no way of telling when the > > whitespace's supposed to be input separator, and when it's just > > a part of filename. > > Oh, come on. Unix shells already have rules for that. You escape the > space, or put the full name in quotes. The problem is that many Unix > tools don't correctly handle filenames with spaces.
Writing strictly from the perspective of a *nix user, please, do not foist that one on me! Again, "Perhaps, you ought to ``correct'' the tools, then impose arbitrary complexity ???" What do you think? -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . .
