"Michael D. Schleif" wrote:
>
> More and more, *nix developers are following the dark path of using
> whitespace in directory and filenames -- something which I've always
> detested, from an sa standpoint ;<
well, it's a valid character, why shouldn't it be there? IMO the
situation where users are limited by arbitrarily limited tools is best
left for win world.
> For example, on my upgraded potato box I may want to do something this
> simple:
>
> grep pump `find /etc/ -type f`
grep rock "`find . -type f`"
or use print0 option with xargs -0 (already suggested in another
post).
> Normally, this is a quick and effective search and I am satisfied and
> can get on with other business.
well, it's quick and dirty because it only works with filenames that
are fairly limited.
> However, now we have abominations, like these:
>
> /etc/X11/afterstep/hookdir/Debian/Apps/Net/Netscape/Communicator(static
> 4.77) Browser
> /etc/X11/afterstep/hookdir/Debian/WindowManagers/Window Maker
> /etc/kde2/colors/40 Colors
>
> Even this, obviously, is *not* an answer:
>
> grep pump `find /etc/ -type f |\
> sed 's! !\\ !g; s!^!"!; s!$!"!'`
>
> How do others handle this?
>
> What do you think?
generally, filename should be allowed to be basically any text. I see
no reason to limit it (well, the general consesnsus among most of the
unix(-like) implementations is that you cannot include '\0' and '/').
And I see no reason to put limits on this because of inadequate tools...
it's the tools that need to be fixed, not filenames.
erik
