Greg Shenaut <[EMAIL PROTECTED]> types:
> In message <[EMAIL PROTECTED]>, void cleopede:
> >On Tue, Oct 02, 2001 at 07:19:37AM -0700, Greg Shenaut wrote:
> >> Is there any reason why the "unbreakable space" (0xa0) shouldn't be
> >> the only kind of space character used/allowed in filenames?
> >Any character except for '/' is allowed in filenames, and I believe it's
> >been that way since the dawn of time.
You can't use nul either, and both have been true since v6.
> Yes, but I mention it because if 0xa0 were used instead of space
> in filenames, then they wouldn't be split into several arguments
> and nothing special would need to be done in "for x in * ;" loops
> or elsewhere to handle them, but the names would still look the same
> to users.
All the other characters that are magic to the shell - newline being
the obvious example - will still cause problems. If you're going to
use this to solve the problem, you need to go to something live VMS or
MVS, and limit file names to alphanumerics plus a small set of
delimiters.
The usual solution for this kind of thing is to extend the
shell. Shell scripts kept breaking trying tod deal with arguments with
strange characters in them until the "$@" mechanism was added. I
wonder how many scripts would break - or stop breaking :-) if we
changed the shell so that "*" expanded like "$@"?
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Q: How do you make the gods laugh? A: Tell them your plans.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
