9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] another dusty upas question
Date: Fri,  2 May 2008 12:59:55 -0400	[thread overview]
Message-ID: <c9cc29ac8dfea8cfeeb3eb53669098c2@quanstro.net> (raw)
In-Reply-To: <20080502164839.CE21B1E8C4D@holo.morphisms.net>

>> however, i'm not sure i fully understand the situation.  why does
>> 	echo fu | upas/marshal -Fs bar quanstro/baz
>> deliver the copy to
>> 	/mail/box/quanstro/(f/)?quanstro_baz
>> and not
>> 	/mail/box/quanstro/baz/(f/)?quanstro
>> where it would land if i filed it after-the-fact with nedmail.
>
> Now you're into weird special cases.
> How did you find the marshal -F flag, anyway?
> It's not documented that I can see.
> Maybe it should just be deleted.  What uses it?

☺.  i found it by reading the source.  i was trying to track
down all the places where mailboxes are fidded in the upas
source.

it does seem very wierd and marshal does a shimmy to
pull it off.  it would seem the only way to file outgoing
& incoming mail to/from the same person in the same
file.

(offtopic: there are at least a few other crunchy bits.
several copies of cistrn?cmp by various names.  there's
also a reference to an rmail program in send/main.c
does it (did it) exist on plan 9?)

- erik




  reply	other threads:[~2008-05-02 16:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 13:29 erik quanstrom
2008-05-02 14:05 ` Russ Cox
2008-05-02 14:10   ` erik quanstrom
2008-05-02 14:23     ` Russ Cox
2008-05-02 15:22       ` erik quanstrom
2008-05-02 16:45         ` Russ Cox
2008-05-02 16:59           ` erik quanstrom [this message]
2008-05-02 17:30             ` Russ Cox
2008-05-02 17:35               ` erik quanstrom
2008-05-02 17:47                 ` Russ Cox
2008-05-02 19:31               ` erik quanstrom
2008-05-02 21:43                 ` Russ Cox
2008-05-02 21:50                   ` erik quanstrom

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=c9cc29ac8dfea8cfeeb3eb53669098c2@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).