From: dsg@mitre.org (David S. Goldberg)
Subject: Re: MIME preview
Date: 03 Mar 1999 10:45:07 -0500 [thread overview]
Message-ID: <m1b1zj6d1bw.fsf@blackbird.mitre.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "03 Mar 1999 16:16:57 +0100"
> Weeell... type C-c C-d then look in the drafts group.
Nope. C-c C-d just leaves the MML in there. It doesn't generate the
actual MIME.
I've been doing M-: (mml-generate-mime) and looking in the
Message-Log, but that's *very* unsatisfying. This is especially
important now, when most MML that isn't a simple "attach this file"
has to be done by hand and it's easy to screw up, even with the
emacs-mime info file open to the example page :-). For example a long
time ago I used a Mac emulation called MAE that saved files in
appledouble format. Occasionally I'm asked to email one of the old
documents to someone. To do so, I have to set up a
multipart/appledouble with the two subparts, one application/applefile
the other application/whatever. I'd like to be able to verify for
myself that I've done it right before it gets sent. The new M-m
keymap (which appears to be unimplemented in 0.79, or do I need to set
up some autoloads?) with its mml-validate function may do what I want,
but it doesn't seem to be there yet.
--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-03-03 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-03 15:03 Simon Josefsson
1999-03-03 15:16 ` Kai.Grossjohann
1999-03-03 15:36 ` Simon Josefsson
1999-03-03 16:16 ` Kai.Grossjohann
1999-03-03 16:20 ` Lee Willis
1999-03-03 15:45 ` David S. Goldberg [this message]
1999-03-03 19:40 ` James H. Cloos Jr.
1999-03-04 1:32 ` Lars Magne Ingebrigtsen
1999-03-04 1:31 ` Lars Magne Ingebrigtsen
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=m1b1zj6d1bw.fsf@blackbird.mitre.org \
--to=dsg@mitre.org \
/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).