From owner-freebsd-hackers Tue Oct 2 22:40:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-203-60.mmcable.com [65.31.203.60]) by hub.freebsd.org (Postfix) with SMTP id 9739037B405 for ; Tue, 2 Oct 2001 22:40:48 -0700 (PDT) Received: (qmail 32836 invoked by uid 100); 3 Oct 2001 05:40:42 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <15290.42202.766797.460932@guru.mired.org> Date: Wed, 3 Oct 2001 00:40:42 -0500 To: gkshenaut@ucdavis.edu Cc: hackers@FreeBSD.ORG Subject: Re: ALT- (Was: how to make 'for' understand two words as a single argumen) In-Reply-To: <200110021841.f92IfVS07537@thistle.bogs.org> References: <20011002185518.A335@firedrake.org> <200110021841.f92IfVS07537@thistle.bogs.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Shenaut types: > In message <20011002185518.A335@firedrake.org>, 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 b= e > >> 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=A0x=A0in=A0*=A0;" l= oops > 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 "$@"? =09=09=09=09http://www.mired.org/home/mwm/ Q: How do you make the gods laugh?=09=09A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message