From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 27 Apr 2011 09:16:36 -0400
To: digbyt@acm.org, 9fans@9fans.net
Message-ID: <80660070788d5c9db6af9f2881e5444d@ladd.quanstro.net>
In-Reply-To: <20110427131041.GA21774@skaro.cthulhu.dircon.co.uk>
References: <86ipu0evi2.fsf@cmarib.ramside>
	<BANLkTimo8Q8zKhqmUwvkJKy14P5dZXVh8w@mail.gmail.com>
	<201104262052.36817.dexen.devries@gmail.com>
	<BANLkTin8cLpwEjoXuvpNe_4ewSUhv-pqEQ@mail.gmail.com>
	<20110427131041.GA21774@skaro.cthulhu.dircon.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] spaces in filenames
Topicbox-Message-UUID: d648c726-ead6-11e9-9d60-3106f5b1d025

On Wed Apr 27 09:12:15 EDT 2011, digbyt@acm.org wrote:
> I was always happy with the traditional Unix approach - Kernel allows
> anything unless there is a good reason not to (ie no NULL or '/').
> Anything else is an application problem that usually required
> some ingenuity if you really wanted to break convention.

port/chan.c:/^char isfrog

- erik