From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
Date: Thu, 30 May 2002 11:13:17 -0700 [thread overview]
Message-ID: <50dde53c4ee179b167e800824a3e6d8f@collyer.net> (raw)
Vowels at least don't bugger parsing and don't require the use of
quoting schemes, which will become increasingly complicated to deal
with embedded spaces, newlines, slashes, and NUL bytes, and which will
make hex file names look appealing. Vowels can stay. ☺
next reply other threads:[~2002-05-30 18:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 18:13 Geoff Collyer [this message]
2002-05-31 4:53 ` Lucio De Re
2002-05-31 8:59 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 10:29 Fco.J.Ballesteros
2002-06-06 10:48 ` Axel Belinfante
2002-06-06 8:11 Fco.J.Ballesteros
2002-06-06 10:22 ` Axel Belinfante
2002-06-05 18:39 Geoff Collyer
2002-06-05 17:55 rog
2002-06-05 17:04 anothy
2002-06-05 13:46 Russ Cox
2002-06-03 7:48 Fco.J.Ballesteros
2002-06-03 16:05 ` Dan Cross
2002-06-05 10:05 ` Douglas A. Gwyn
2002-06-01 21:37 jmk
2002-06-01 22:06 ` Dan Cross
2002-05-30 22:01 forsyth
2002-05-30 20:16 rog
2002-05-30 20:14 rsc
2002-05-30 19:29 rog
2002-05-30 19:12 forsyth
2002-05-30 18:58 rog
2002-05-30 18:55 rsc
2002-05-30 18:16 rog
2002-06-04 16:23 ` Axel Belinfante
2002-05-30 18:15 rsc
2002-05-30 18:09 Sape Mullender
2002-05-30 17:58 Fco.J.Ballesteros
2002-05-30 17:10 ` Sam
2002-05-30 17:52 presotto
2002-05-30 17:46 Geoff Collyer
2002-05-30 17:00 Fco.J.Ballesteros
2002-06-01 21:34 ` Dan Cross
2002-05-30 16:57 Fco.J.Ballesteros
2002-05-30 17:03 ` Lucio De Re
2002-06-05 9:55 ` Douglas A. Gwyn
2002-05-30 16:30 rsc
2002-05-30 16:35 ` Axel Belinfante
2002-06-05 9:54 ` Douglas A. Gwyn
2002-05-30 16:30 rsc
2002-05-30 16:21 Axel Belinfante
2002-05-30 16:27 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50dde53c4ee179b167e800824a3e6d8f@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).