From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <12909a681fa7ea20d2bb4c6c1dfac0f0@plan9.bell-labs.com>
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed,  5 Jun 2002 08:46:59 -0500
Topicbox-Message-UUID: a6055874-eaca-11e9-9e20-41e7f4b1d025

> > Everything starts to break when you deal with spaces
> > in file names.

> I find that interesting since it sounds like regression instead of
> progress.

this is a stupid discussion, but who am i to stop it?

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.  for example, if i
click on this line:

	/usr/rsc/lib/profile

in acme, i don't want it to expand the selection back
and forward until it hits the two apostrophes in my
do not contractions.  so in those contexts, spaces
in file names do break everything.

my point was that acme (and to a lesser extent,
plumbing) don't interact well with spaces in file names.
this is a fundamental problem.

you can pick your poison.  acme employs sensible
defaults that make my editing and interaction with
the system a whole lot easier.  i won't give them up
just to get spaces in my file names.

russ