From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: [9fans] frogs and osx
Date: Thu, 3 Jan 2008 19:46:09 +0000 [thread overview]
Message-ID: <33bbf51a2f464189183909eb31c415b8@quintile.net> (raw)
Hi,
Using u9fs to access my mac I find I cannot see directories (folders)
that have their own specific icon.
This turns out to be because these directories contain a file
Icon<cr> whiel <cr> is ASCII 13, and /sys/src/9/port/chan.c:1656
defines the frogs illegal in filenames to include carriage return.
Why does frogs contain these latters, My feeling is that only <nul>
should be illegal, perhaps these are a hangover from pre utf-8
days?
Perhaps there is a good reason for not allowing such characters,
I can see that creating such files should be discouraged but
failing a read(2) of a directory containing such files seems extreme.
Is it historic or there for a very good reason™ ?
-Steve
next reply other threads:[~2008-01-03 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 19:46 Steve Simon [this message]
2008-01-04 2:29 ` Russ Cox
2008-01-04 6:35 ` Bruce Ellis
2008-01-04 7:24 ` Lyndon Nerenberg
2008-01-04 7:31 ` Bruce Ellis
2008-01-04 7:37 ` Lyndon Nerenberg
2008-01-04 7:45 ` Bruce Ellis
2008-01-04 7:45 ` Lyndon Nerenberg
2008-01-04 9:52 ` Bruce Ellis
2008-01-04 10:17 ` Steve Simon
2008-01-04 10:26 ` Bruce Ellis
2008-01-04 11:22 ` Pietro Gagliardi
2008-02-06 13:51 ` underspecified
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=33bbf51a2f464189183909eb31c415b8@quintile.net \
--to=steve@quintile.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).