From: Tim Wiess <tim@nop.cx>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme mail on unix
Date: Wed, 18 Jan 2006 10:08:36 -0800 [thread overview]
Message-ID: <3443d62729894fab917771e5b74ae696@akira.nop.cx> (raw)
In-Reply-To: <05f36861c20b652d1fb8127b2e9a5c7e@akira.nop.cx>
oops, sorry for the noise, didn't mean to send this to the list.
> Russ,
> This is great! I am very eager to try this out.
> However I didn't get the Mail script you attached. It just
> came through as an empty file. Would you mind sending that
> again?
>
> tim
>
>
> > I am sending this from inside acme Mail on Linux.
> > Or at least the program is called Mail.
> > It's not actually the Mail from Plan 9.
> >
> > I am running mh and have 'customized' it to print
> > something close to sensible output. Mail itself
> > is a shell script. The interactive delay is a little
> > annoying sometimes, you have to run inc and Get
> > to check for new mail, and the script itself needs
> > to be cleaned up, but it's still entirely usable.
> >
> > I have attached my .mh_profile, Mail/mhl.format,
> > Mail/mhl.headers, and the Mail script itself.
> >
> > Russ
next prev parent reply other threads:[~2006-01-18 18:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 16:46 Russ Cox
2006-01-18 17:56 ` Tim Wiess
2006-01-18 18:08 ` Tim Wiess [this message]
2006-01-18 19:10 ` Russ Cox
2006-01-19 16:17 ` Aaron Griffin
2006-01-19 16:24 ` Russ Cox
2006-01-19 21:28 ` Dan Cross
2006-01-19 21:58 ` Russ Cox
2006-01-20 2:38 ` geoff
2006-01-20 5:31 ` Scott Schwartz
2006-01-20 6:04 ` John Barham
2006-01-20 13:50 ` erik quanstrom
2006-01-20 23:01 ` Dave Eckhardt
2006-01-21 0:06 ` erik quanstrom
2006-01-20 13:58 ` erik quanstrom
2006-01-20 20:02 ` erik quanstrom
2006-01-20 20:12 ` uriel
2006-01-20 20:18 ` erik quanstrom
2006-01-20 20:41 ` uriel
2006-01-20 20:59 ` erik quanstrom
2006-01-20 22:58 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=3443d62729894fab917771e5b74ae696@akira.nop.cx \
--to=tim@nop.cx \
--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).