From: "erik quanstrom" <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "Russ Cox" <rsc@swtch.com>
Subject: Re: [9fans] rfork(RFPROC) and ffork()
Date: Sat, 29 Oct 2005 18:00:45 -0500 [thread overview]
Message-ID: <20051029230045.D2855243E@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0510291218vd769a7bn7fd05110ac519e74@mail.gmail.com>
thanks for the information. i'll take a look at upas.
the reason i was looking into faces is because i just wrote
a (not-so-simple-anymore) maildir mail "reader". it's vaguely like nedmail
(from what i've read) except each command is a seperate executable.
e.g.
; thread
mcat $m/1130599988.10533* # 2005.10.29 10:08 "Russ Cox" <rsc@swtc [9fans] 386
mcat $m/1130612580.12213* # 2005.10.29 14:07 "William Josephson"
mcat $m/1130624105.13127* # 2005.10.29 15:01 jmk@plan9.bell-labs.
mcat $m/1130624106.13151* # 2005.10.29 15:06 "Lucio De Re" <lucio
where each line of thread output is ment to be cut-and-pasted.
(there's also fwd, reply, mdesc, attachments, and detach.)
it's a little clunky right now. and it's not a p9p program because
i wanted to use it on a couple of linux machines that don't have p9p
installed and most mail readers require cursor addressing. It could
be, though if i converted the "long" print formats
btw, why does upas use the mbox format rather than a directory?
just wondering.
Russ Cox <rsc@swtch.com> writes
|
| Ffork is gone; use libthread instead. I've updated the message.
|
| As for faces, John Cummings has a working faces. I'm hoping
| he will send it to me so I can include it in the distribution.
| He also got upas and acme mail running enough to read
| mail (I believe via pop or imap) on his system. I've checked
| in the code to CVS. It may need some cleaning up (any volunteers?)
| and is not built by default, but it's there. See
| src/cmd/upas and src/cmd/acme/mail.
|
| Russ
next prev parent reply other threads:[~2005-10-29 23:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 15:34 erik quanstrom
2005-10-29 19:11 ` William Josephson
2005-10-29 19:18 ` Russ Cox
2005-10-29 23:00 ` erik quanstrom [this message]
2005-10-29 23:24 ` Francisco J Ballesteros
2005-10-29 23:38 ` Russ Cox
2005-10-30 0:19 ` erik quanstrom
2005-10-30 1:07 ` Russ Cox
2005-10-30 1:15 ` Ronald G Minnich
2005-10-30 1:22 ` geoff
2005-10-30 1:58 ` jmk
2005-10-30 1:54 ` Dave Eckhardt
2005-10-30 2:24 ` erik quanstrom
2005-10-30 2:51 ` geoff
2005-10-30 1:10 ` geoff
2005-10-30 1:18 ` Paul Lalonde
2005-10-30 6:52 ` Skip Tavakkolian
2005-10-30 10:14 ` Francisco J Ballesteros
2005-10-30 15:17 ` Russ Cox
2005-10-30 23:00 ` Dave Eckhardt
2005-10-30 23:14 ` George Michaelson
2005-10-31 2:15 ` erik quanstrom
2005-10-31 2:33 ` geoff
2005-10-31 3:23 ` Skip Tavakkolian
2005-10-31 4:20 ` Lyndon Nerenberg
2005-10-31 21:31 ` Dave Eckhardt
2005-10-31 4:06 ` [9fans] Scaleable mail repositories Lyndon Nerenberg
2005-10-31 10:55 ` C H Forsyth
2005-10-31 12:32 ` erik quanstrom
2005-11-01 19:56 ` rog
2005-11-01 22:29 ` Francisco J Ballesteros
2005-11-08 19:56 ` rog
2005-11-08 23:22 ` Joel Salomon
2005-11-09 0:51 ` Caerwyn Jones
2005-11-09 0:55 ` Russ Cox
2005-11-09 3:32 ` erik quanstrom
2005-10-31 15:30 ` jmk
2005-10-30 1:10 ` [9fans] rfork(RFPROC) and ffork() William Josephson
2005-10-31 14:48 ` Russ Cox
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=20051029230045.D2855243E@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).