From owner-freebsd-hackers Wed Oct 3 9:12:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with SMTP id 37AFA37B401 for ; Wed, 3 Oct 2001 09:12:39 -0700 (PDT) To: Warner Losh Cc: gkshenaut@ucdavis.edu, hackers@FreeBSD.ORG Received: From MAIL.TVOL.NET (10.1.1.4[10.1.1.4 port:1734]) by mx.wgate.comMail essentials (server 2.429) with SMTP id: <34671@mx.wgate.com>transfer for ; Wed, 3 Oct 2001 12:11:05 PM -0400 ;transfer smtpmailfrom X-MESINK_Inbound: 0 X-MESINK_MailForType: SMTP X-MESINK_SenderType: SMTP X-MESINK_Sender: msinz@wgate.com X-MESINK_MailFor: hackers@FreeBSD.ORG Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)id 4BW3ALS8; Wed, 3 Oct 2001 12:11:12 -0400 Received: from wgate.com (localhost [127.0.0.1])by sinz.eng.tvol.net (8.11.6/8.11.6) with ESMTP id f93GCNs28240;Wed, 3 Oct 2001 12:12:23 -0400 (EDT)(envelope-from msinz@wgate.com) Date: Wed, 03 Oct 2001 12:12:23 -0400 From: Michael Sinz Organization: WorldGate Communications Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en Subject: Re: ALT- (Was: how to make 'for' understand two words as a singleargumen) References: <200110022357.f92NvnS08486@thistle.bogs.org> <7fffe3770386f507d1@[192.168.1.4]> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit x-receiver: hackers@FreeBSD.ORG x-sender: msinz@wgate.com MIME-Version: 1.0 Message-ID: <7ffffcf203a07007d1@[192.168.1.4]> 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 Warner Losh wrote: > > 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 I would hope that we don't get into the mapping of characters in the filesystem. Especially when some people read the characters of a filename and push them through something like shifjis (Japan) and get something completely different. BTW - How does your system represent a file with 0xA0 in it? An ls on FreeBSD 4.4-Stable seems to show it as: -rw-r--r-- 1 msinz msinz 0 Oct 3 12:00 foo?bar Interesting - not what I would have expected but I think "non-printables" are replaced by the "?" when ls runs. Even more interesting is this: -rw-r--r-- 1 msinz msinz 0 Oct 3 12:00 foo?bar -rw-r--r-- 1 msinz msinz 1 Oct 3 12:05 foo?bar (one has a linefeed in the name and one has a non-breaking space in the name) -- Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message