From mboxrd@z Thu Jan  1 00:00:00 1970
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <20020605171109.11A0119AAC@mail.cse.psu.edu>
Date: Wed,  5 Jun 2002 13:04:09 -0400
Topicbox-Message-UUID: a66d74b8-eaca-11e9-9e20-41e7f4b1d025

//the things that break are mainly things like
//plumbing and acme tag windows, which derive their
//power from the fact that they treat all text
//equally and _don't_ have to worry about
//complex state like quoting.

but wouldn't it be reasonable for acme/plumbing/etc. to
hold onto this assumption, unless instructed otherwise?
i mean, sure, i don't want the default text expansion to
go looking for quotes every time i click, but we can
already override the default text expansion by sweeping
out the exact text we want.

it's entirely reasonable to optimize for the comman (and
in this case, simple) case, and have people who want to
uses spaces in file names go through a little extra work
to use these tools. it would seem a much more tractable
problem to make acme/plumbing deal with exact text
strings - as they pretty much do already - which might
include spaces than to try and have them figure out
where the magic delimiters are.
ア