9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] frogs and osx
Date: Fri,  4 Jan 2008 06:22:20 -0500	[thread overview]
Message-ID: <A951A41A-D922-4FCA-9C3F-9E9349E8584F@mac.com> (raw)
In-Reply-To: <E87A0939-AA5A-4D98-BB8F-871A59CF8F10@orthanc.ca>

It's also a pity that you'll need to rewrite your code to handle two  
different types of delimiters then, or add a dellim argument like in  
Brdstr. The UNIX philosophy says to do what's smaller and faster, not  
what's better (which is why I don't like it).

I haven't seen a reason to use the format "icon\rname" in an OS X  
directory. Why not just store the information in the  
folder's .DS_store file (which has every other Finder credential)?  
Ahh, the mysteries of my iMac...

On Jan 4, 2008, at 2:24 AM, Lyndon Nerenberg wrote:

>
> On 2008-Jan-3, at 19:29 , Russ Cox wrote:
>
>> In addition to NUL, surely / should be illegal!
>> I certainly wouldn't want \n in file names; \r seems just too close.
>
> Pathological egregiousness?
>
> There is only one true separator, and that is '/'. In the context  
> of pathnames, '/' is NUL as per C strings. NUL in pathnames is  
> silly, but allowed, as per pathnames.
>
> It makes no sense, but if you can push a NUL into a pathname, you  
> should deal with the result. It's a pity the intermediate code has  
> to do so as well ...


  parent reply	other threads:[~2008-01-04 11:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 19:46 Steve Simon
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 [this message]
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=A951A41A-D922-4FCA-9C3F-9E9349E8584F@mac.com \
    --to=pietro10@mac.com \
    --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).