From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d190801040152n1a239619x7dcdf31796fd181e@mail.gmail.com>
Date: Fri,  4 Jan 2008 20:52:37 +1100
From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] frogs and osx
In-Reply-To: <0056CF0F-5431-456B-89E4-C379EB281ABB@orthanc.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080104022953.CE1461E8C1F@holo.morphisms.net>
	<E87A0939-AA5A-4D98-BB8F-871A59CF8F10@orthanc.ca>
	<775b8d190801032331u69725293lc35b536f2fd3b9a4@mail.gmail.com>
	<0056CF0F-5431-456B-89E4-C379EB281ABB@orthanc.ca>
Topicbox-Message-UUID: 270d3dbc-ead3-11e9-9d60-3106f5b1d025

NO! a frog is a mistake. '\n' and '\r' are both frogs so where did
you get the EOL thing from.  i want neither in my filenames.
if you do then change your copy of the code.  or make up a new
reason not to.  make your own island of tranquility.

brucee

On Jan 4, 2008 6:45 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>
> On 2008-Jan-4, at 00:31 , Bruce Ellis wrote:
>
> > not at all, pragmatic.excluding crap from filenames was and still is
> > good.
> > if you want to vote '\r' as "not a mistake"  you can.  but filenames
> > created
> > from buggy stuff die dead, as they should.
>
> We are arguing different things. EOL conventions are religion.  Kernel
> delimiters are just code.
>