From: Michael R. Wolf <MichaelRunningWolf@att.net>
Subject: Re: Nested mime messages
Date: Fri, 16 May 2003 10:13:16 -0700 [thread overview]
Message-ID: <u3cjezufn.fsf@att.net> (raw)
In-Reply-To: <uhe7vqbzq.fsf@st.alphonsos.pancake.breakfast>
Paul Jensen <usenet@foreignkey.com> writes:
> Michael R. Wolf <MichaelRunningWolf@att.net> writes:
>
>> This reference is amazingly useful, and your posting is amazingly
>> helpful.
>
> Wow -- that is some reference card! Good stuff. It's already been
> useful here at the workplace for amazing my friends and confounding my
> non-Emacs-using enemies... ;)
It's got a kid-proof intro -- "Gnus is complex". I like that.
This is a professional strength tool; wimps need not apply.
--
Michael R. Wolf
All mammals learn by playing!
MichaelRunningWolf@att.net
prev parent reply other threads:[~2003-05-16 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3fzngjt1v.fsf@wivenhoe.staff8.ul.ie>
2003-05-15 12:38 ` Kai Großjohann
[not found] ` <m37k8sjqw9.fsf@wivenhoe.staff8.ul.ie>
[not found] ` <m3k7cstgz3.fsf@defun.localdomain>
[not found] ` <ud6ikx80c.fsf@att.net>
2003-05-15 20:59 ` Jesper Harder
[not found] ` <un0hnsdvw.fsf@att.net>
[not found] ` <uhe7vqbzq.fsf@st.alphonsos.pancake.breakfast>
2003-05-16 17:13 ` Michael R. Wolf [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=u3cjezufn.fsf@att.net \
--to=michaelrunningwolf@att.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).