From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Liberating the filename (Was: [9fans] acme question + diffs for kfs, fs and plumbing)
Date: Tue, 9 Jul 2002 13:01:38 +0200 [thread overview]
Message-ID: <20020709130136.O20312@cackle.proxima.alt.za> (raw)
In-Reply-To: <020b01c22736$fc9d26f0$6501a8c0@xpire>; from matt on Tue, Jul 09, 2002 at 11:54:21AM +0100
On Tue, Jul 09, 2002 at 11:54:21AM +0100, matt wrote:
>
> is # a consideration? It's a valid filename char on FreeBSD
I think it's valid in a Plan 9 filename, but if not, it's easy to
expand the list to deal with it.
Which reminds me, if we use
fpath = (usr lucio fname)
as a future description of a filepath, how do we designate the
root?
fpath = ('' usr lucio fname)
perhaps?
++L
next prev parent reply other threads:[~2002-07-09 11:01 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 7:50 [9fans] acme question + diffs for kfs, fs and plumbing Fco.J.Ballesteros
2002-07-09 8:15 ` Lucio De Re
2002-07-09 8:42 ` arisawa
2002-07-09 9:21 ` Lucio De Re
2002-07-09 9:43 ` arisawa
2002-07-09 10:36 ` Lucio De Re
2002-07-09 10:54 ` matt
2002-07-09 11:01 ` Lucio De Re [this message]
2002-07-09 11:07 ` Liberating the filename (Was: [9fans] acme question + diffs for kfs, fs and plumbing) arisawa
2002-07-11 14:57 ` Liberating the filename (Was: [9fans] acme question + diffs forkfs, Douglas A. Gwyn
2002-07-09 8:22 ` [9fans] acme question + diffs for kfs, fs and plumbing arisawa
-- strict thread matches above, loose matches on Subject: below --
2002-07-10 18:27 [9fans] blanks in file names David Gordon Hogan
2002-07-10 20:56 ` arisawa
2002-07-10 8:00 Fco.J.Ballesteros
2002-07-10 7:57 [9fans] acme question + diffs for kfs, fs and plumbing Fco.J.Ballesteros
2002-07-09 8:42 Fco.J.Ballesteros
2002-07-09 9:28 ` Lucio De Re
2002-07-09 11:23 ` andrey mirtchovski
2002-07-09 12:05 ` matt
2002-07-09 7:54 [9fans] blanks in file names Fco.J.Ballesteros
[not found] ` <Fco.J.Ballesteros@Jul>
2002-07-09 15:23 ` Dave
2002-07-09 15:29 ` [9fans] acme question + diffs for kfs, fs and plumbing Dave
2002-07-10 15:57 ` Dave
2002-07-10 16:02 ` [9fans] blanks in file names Dave
2002-07-10 20:59 ` FJ Ballesteros
2002-07-10 21:51 ` Dave
2002-07-10 22:22 ` Dan Cross
2002-07-10 23:01 ` Dave
2002-07-11 2:00 ` Dan Cross
2002-07-11 6:14 ` Dave
2002-07-11 6:38 ` Lucio De Re
2002-07-14 18:00 ` Dave
2002-07-11 13:14 ` arisawa
2002-07-12 12:28 ` arisawa
2002-07-11 16:23 ` Dan Cross
2002-07-11 10:43 ` Ish Rattan
2002-07-14 18:49 ` Dave
2002-07-03 8:00 Fco.J.Ballesteros
2002-07-03 12:00 ` Lucio De Re
2002-07-03 19:39 ` rob pike, esq.
2002-07-07 4:02 ` Dave
2002-07-07 5:17 ` arisawa
[not found] ` <"arisawa@ar.aichi-u.ac.jp"@Jul>
2002-07-07 5:38 ` Dave
2002-07-07 6:04 ` arisawa
2002-07-07 7:16 ` arisawa
2002-07-07 16:11 ` Dave
2002-07-07 16:12 ` Dave
2002-07-09 15:31 ` [9fans] acme question + diffs for kfs, fs and plumbing Dave
2002-07-09 22:15 ` arisawa
2002-07-10 21:58 ` [9fans] blanks in file names Dave
2002-07-10 22:38 ` arisawa
2002-07-10 22:42 ` [9fans] " Jim Choate
2002-07-11 5:08 ` Dave
2002-07-11 5:10 ` [9fans] " Dave
2002-07-14 18:32 ` Dave
2002-07-14 18:51 ` Jim Choate
2002-07-14 23:27 ` arisawa
2002-07-08 9:48 ` Boyd Roberts
2002-07-08 20:22 ` Dave
2002-07-09 8:24 ` Boyd Roberts
2002-07-09 15:25 ` Dave
2002-07-08 23:05 ` Berry Kercheval
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=20020709130136.O20312@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).