From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Why is MIME hard?
Date: Fri, 28 Sep 2007 11:42:47 -0400 [thread overview]
Message-ID: <jwvfy0y23wb.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 1190902460.055800.73670@y42g2000hsy.googlegroups.com
> The oft-quoted page http://bmrc.berkeley.edu/~trey/emacs/mime.html
> seems to have stopped existing and I have been through the Emacs MIME
> manual. But the real reason for posting this here is my inability to
> guess a philosophy behind making MIME so hard in Emacs. Can't it be
> any simpler? Also, someone commented on comp.mail.mime that I had to
> "let go of Rmail and use Gnus or Mew instead" if I wanted MIME. Is
> that really so?
I believe the reason is just that there hasn't been much work on Rmail.
Stefan
next prev parent reply other threads:[~2007-09-28 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 14:14 Why is MIME hard? Girish Kulkarni
2007-09-27 19:15 ` Reiner Steib
2007-09-27 20:52 ` Eli Zaretskii
2007-09-28 7:17 ` Dmitri Minaev
2007-09-28 15:42 ` Stefan Monnier [this message]
2007-09-30 13:28 ` Tim X
2007-09-30 14:38 ` Reiner Steib
2007-10-02 7:03 ` Tim X
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfy0y23wb.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).