From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Douglas A. Gwyn" <DAGwyn@null.net>
Message-ID: <3CF7E38C.64F9B1AB@null.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <3ca77c62df7c1f26a1601d02c632efde@plan9.bell-labs.com>
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
Date: Wed,  5 Jun 2002 09:54:46 +0000
Topicbox-Message-UUID: a58eb5ac-eaca-11e9-9e20-41e7f4b1d025

rsc@plan9.bell-labs.com wrote:
> Everything starts to break when you deal with spaces
> in file names.

I find that interesting since it sounds like regression instead of
progress.
On Unix, the only real problem with spaces in file names was in avoiding
inappropriate parsing of arguments on shell command lines, usually
addressed
by 'quoting'.  Note also that the "xargs" utility, otherwise extremely
useful, was misimplemented in that it did not quote arguments before
invoking commands via a subshell.  (Proper quoting is tricky since there
can be embedded ' " \ NL, etc.  Much better would be to simply pass the
arguments uninterpreted via execv().)