From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] APPLIX-L On this day... (Rosetta Stone, Einstein's equation, first Model T, first passenger train)
Date: Wed, 27 Sep 2017 22:52:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1709272251460.21809@frieza.hoshinet.org> (raw)
In-Reply-To: <alpine.BSF.2.21.1709281056410.47452@aneurin.horsfall.org>
On Thu, 28 Sep 2017, Dave Horsfall wrote:
> On Wed, 27 Sep 2017, Roland Turner wrote:
>
>> * Simply attaching the entire message as a message/rfc822 part is an
>> appealing approach, but very few mail clients would do anything
>> intelligent with it.
>
> My MUA of choice, Alpine, certainly does, and it's hardly uncommon. I tried
> Elm once, and immediately went straight back to Pine (as it was known then);
> never bothered with Mutt.
20 years and I'm still using Pine/Alpine myself. XD
-uso.
prev parent reply other threads:[~2017-09-28 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.BSF.2.21.1709270653590.42298@aneurin.horsfall.org>
[not found] ` <2af88ebe-a372-6a4a-87ee-49e1533aa1dd@acfr.usyd.edu.au>
[not found] ` <15bb0682-4366-cfc5-8133-6b1292830c03@rolandturner.com>
2017-09-28 1:07 ` Dave Horsfall
2017-09-28 2:52 ` Steve Nickolas [this message]
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=alpine.BSF.2.02.1709272251460.21809@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).