From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xah Newsgroups: gmane.emacs.help Subject: Re: (emacs+unix): How to have a file-name containing slashes, angle-brackets, etc? Date: Tue, 26 Aug 2008 01:42:50 -0700 (PDT) Organization: http://groups.google.com Message-ID: <6c61b7dc-2bc2-4b22-8153-fb858cd2fab8@t1g2000pra.googlegroups.com> References: <9e31b345-4cec-4ea6-8d63-d66b8355da06@p10g2000prf.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1219743720 4189 80.91.229.12 (26 Aug 2008 09:42:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 26 Aug 2008 09:42:00 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Aug 26 11:42:53 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KXv4e-0000c0-6f for geh-help-gnu-emacs@m.gmane.org; Tue, 26 Aug 2008 11:42:52 +0200 Original-Received: from localhost ([127.0.0.1]:52825 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KXv3e-0006al-No for geh-help-gnu-emacs@m.gmane.org; Tue, 26 Aug 2008 05:41:51 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!t1g2000pra.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 76 Original-NNTP-Posting-Host: 24.6.185.159 Original-X-Trace: posting.google.com 1219740170 30293 127.0.0.1 (26 Aug 2008 08:42:50 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 26 Aug 2008 08:42:50 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: t1g2000pra.googlegroups.com; posting-host=24.6.185.159; posting-account=bRPKjQoAAACxZsR8_VPXCX27T2YcsyMA User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.2 Safari/525.22, gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:161652 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:56992 Archived-At: On Aug 25, 1:13 pm, Nikolaj Schumacher wrote: > According to Wikipedia, EXT2 (1993) supports all characters. Older data > is harder to find. unix uses UFS. if i recall correctly, the ext2 didn't become popular until mid 2000. don't want to argue... you can read more about unix issues on my site... Xah =E2=88=91 http://xahlee.org/ =E2=98=84 Nikolaj Schumacher wrote: > Xah wrote: > > > On Aug 24, 5:31 am, Nikolaj Schumacher wrote: > >> Xah wrote: > >> > Unix is the worst, they pretty much just allow > >> > alphanumerics and not even space. If you have anything like =E2=80= =9C,=3D(); > >> > \'"~&-=E2=80=9D etc, you can expect most shell tools to erase you di= sk) > >> > >> Actually unix systems allow pretty much every character except / and t= he > >> null character. > > > > To say that unix allows much wider chars in file names is like saying > > mud is the best medium for sculpture. > > No, actually its not like that at all. That would be an opinion, while > I stated a (verifiable/refutable) fact. > > > Unix file names, for much of its history up to perhaps mid 2000s, > > effectively just allows alphanumerics plus hyphen =E2=80=9C-=E2=80=9D a= nd underscore > > =E2=80=9C_=E2=80=9D. > > According to Wikipedia, EXT2 (1993) supports all characters. Older data > is harder to find. > > What do you mean by the vague term "effectively"? > > > Sure, you can use many non-alphanumeric chars besides hyphen and > > underscore in unix, but the system is simply not designed for it. > > Please explain where the design falls short. > > > Majority of unix tools, including file name listing, will chock and > > break if your filename contain these chars. The chocking doesn't > > actually give you a nice error message, but silently break and often > > resulting in unexpected and unpredicable behavior. In short, it's just > > not designed for it. > > $ touch "=3D;\\'\"~&-=E2=80=9C,$#\!*()=E2=80=9D =E2=84=A2=C2=AE=C2=A9=C2= =A3=C2=A2=E2=89=88=E2=88=AB=C2=B5=E2=88=82=C6=92=CF=80=E2=89=A0=E2=89=A4=E2= =89=A5=E2=88=9E=C2=AB=C2=BB=C2=A1=E2=80=A0=E2=80=A1=C2=B0=C3=A7=C3=B6" > $ ls > =3D;\'"~&-=E2=80=9C,0\!*()=E2=80=9D =E2=84=A2=C2=AE=C2=A9=C2=A3=C2=A2=E2= =89=88=E2=88=AB=C2=B5=E2=88=82=C6=92=CF=80=E2=89=A0=E2=89=A4=E2=89=A5=E2=88= =9E=C2=AB=C2=BB=C2=A1=E2=80=A0=E2=80=A1=C2=B0=C3=A7=C3=B6 > $ rm "=3D;\\'\"~&-=E2=80=9C,$#\!*()=E2=80=9D =E2=84=A2=C2=AE=C2=A9=C2=A3= =C2=A2=E2=89=88=E2=88=AB=C2=B5=E2=88=82=C6=92=CF=80=E2=89=A0=E2=89=A4=E2=89= =A5=E2=88=9E=C2=AB=C2=BB=C2=A1=E2=80=A0=E2=80=A1=C2=B0=C3=A7=C3=B6" > > No problem there. > > > > regards, > Nikolaj Schumacher