From owner-freebsd-hackers Tue Oct 2 21:31: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 735C237B401 for ; Tue, 2 Oct 2001 21:31:05 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f934V4u76744; Tue, 2 Oct 2001 22:31:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f934V4718445; Tue, 2 Oct 2001 22:31:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110030431.f934V4718445@harmony.village.org> To: gkshenaut@ucdavis.edu Subject: Re: ALT- (Was: how to make 'for' understand two words as a single argumen) Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 02 Oct 2001 16:57:49 PDT." <200110022357.f92NvnS08486@thistle.bogs.org> References: <200110022357.f92NvnS08486@thistle.bogs.org> Date: Tue, 02 Oct 2001 22:31:03 -0600 From: Warner Losh 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 In message <200110022357.f92NvnS08486@thistle.bogs.org> Greg Shenaut writes: : But you have to admit, space is a character that has caused many : problems in Unix filenames, because of the other Unix tradition of : space-delimited word record handling. I usually use an underscore, : myself, if I want a space-like separation in a filename, but I : could (and have) used 0xa0 for a similar purpose. : : Just out of curiosity, what would be an instance where you have : wanted a space in a filename and wouldn't have been satisfied with : 0xa0 instead of 0x20? Where 0xa0 doesn't exist in the local? To be honest, up until this thread I'd never heard of ASCII defining a unbreakable space as 0xa0. That's because ASCII doesn't define it (but ISO 8859-1 might). I also have a bad feeling that this might have implications for NFS file systems as well where 0xa0 and 0x20 might mean different things to the remote host. And what about '"`~<>?[]{}\|)(*&^$ as well. All of these (and maybe others) can cause problems as well. In short, fix the broken shell scripts, not the filesystem. You aren't fixing the real problem, just one small slice of it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message