From: Alexander Pohoyda <alexander.pohoyda@gmx.net>
Cc: rms@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: [rmail-mbox-branch]: mail-utils
Date: 09 Oct 2004 18:04:04 +0200 [thread overview]
Message-ID: <878yafj2tn.fsf@oak.pohoyda.family> (raw)
In-Reply-To: <20041008234741.GA17298@fencepost>
Miles Bader <miles@gnu.org> writes:
> On Sat, Oct 09, 2004 at 01:34:49AM +0200, Alexander Pohoyda wrote:
> > > The mm- stuff seems not to be intended to be gnus-specific, but rather
> > > general-purpose code for handling mime that happens to be developed as part
> > > of gnus.
> >
> > Yes, I understand the intention.
> >
> >
> > > There are probably a few dependencies on gnus that have crept in, but I
> > > presume these could be excised.
> >
> > Some mm-*.el files use quite often functions or constants with gnus-
> > prefix.
>
> Can you be more specific? I did a grep, and the dependencies seem pretty
> much restricted to a few files (e.g., mm-view.el);
Yes, there are only very few cases:
mm-partial.el:(require 'gnus-sum)
mm-partial.el: (set-buffer gnus-summary-buffer)
mm-partial.el: (gnus-request-article-this-buffer (aref header 0)
mm-partial.el: (gnus-summary-article-number))))
mm-partial.el: (setq gnus-article-mime-handles
mm-partial.el: (append (if (listp (car gnus-article-mime-handles))
mm-partial.el: gnus-article-mime-handles
mm-partial.el: (list gnus-article-mime-handles))
mm-partial.el: (run-hooks 'gnus-article-decode-hook)
mm-partial.el: (gnus-article-prepare-display)
mm-uu.el: :group 'gnus-article-mime)
mm-view.el: (autoload 'gnus-article-prepare-display "gnus-art")
mm-view.el: (run-hooks 'gnus-article-decode-hook)
My primary concern, however, is that mm- stuff is rather a MIME
parser (viewer), while rfc*.el files implement basic functions.
Wouldn't it be good to have these two things clearly separated?
If we don't separate mm- and basic MIME functions, and if we don't
move them out of gnus directory, people will continue to re-implement
basic functions.
Do you know of any good reason to have the mm-* stuff used in rfc*
files?
Anyway, we need MIME support in Rmail. Would it be correct to make
Rmail depend on file from Gnus directory? My idea is to move MIME
stuff into lisp/mail(/mime?) directory. Both Gnus and Rmail could use
these basic functions. All I propose to move, are few files:
lisp/gnus/rfc2045.el
lisp/gnus/rfc2047.el
lisp/gnus/rfc2231.el
leaving mm-* files intact. What exactly do you disagree with?
> > I would like to have a clean MIME library first.
>
> Sure, and the mm- stuff seems like the right to start from.
By "MIME library" I mean functions like
rfc2045-qp-decode-string,
rfc2231-decode-string,
rfc2047-decode-region
but not
mm-inline-partial,
mm-inline-image-xemacs,
mm-setup-w3,
mm-inline-message
> would completely silly to reimplement all of it when mm- is pretty
> close to what you want anyway.
People may have their own ideas how to use MIME, let's not force them
to use mm- as a bonus.
--
Alexander Pohoyda <alexander.pohoyda@gmx.net>
PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44
next prev parent reply other threads:[~2004-10-09 16:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1096006177.432792.29828.nullmailer@Update.UU.SE>
[not found] ` <m3mzzgw2za.fsf@kfs-l.imdomain.dk>
[not found] ` <1096014084.739640.30529.nullmailer@Update.UU.SE>
[not found] ` <m3fz58vx3l.fsf@kfs-l.imdomain.dk>
[not found] ` <E1CB6fb-0004I5-Ud@fencepost.gnu.org>
[not found] ` <200410031040.i93Ae1YS000609@oak.pohoyda.family>
[not found] ` <E1CEUc7-0003aQ-C3@fencepost.gnu.org>
[not found] ` <87d5zvwmq9.fsf_-_@oak.pohoyda.family>
[not found] ` <20041006214742.GA5180@fencepost>
[not found] ` <87mzywyeau.fsf@oak.pohoyda.family>
2004-10-08 23:47 ` Miles Bader
2004-10-09 16:04 ` Alexander Pohoyda [this message]
2004-10-09 17:12 ` Stefan
2004-10-09 18:15 ` Alexander Pohoyda
2004-10-09 18:20 ` Miles Bader
[not found] ` <878yaf61x0.fsf@oak.pohoyda.family>
2004-10-09 21:10 ` Miles Bader
2004-10-09 21:19 ` Miles Bader
2004-10-10 15:15 ` Richard Stallman
2004-10-10 22:58 ` Miles Bader
2004-10-11 16:45 ` Richard Stallman
2004-10-12 2:09 ` Miles Bader
[not found] ` <87is9gj8v5.fsf@jurta.org>
[not found] ` <20041012150351.GA24206@fencepost>
2004-10-12 16:05 ` Syncing Gnus with Emacs and back (was: [rmail-mbox-branch]: mail-utils) Reiner Steib
2004-10-13 1:26 ` Syncing Gnus with Emacs and back Miles Bader
2004-10-13 20:21 ` Reiner Steib
2004-10-13 22:51 ` Miles Bader
2004-10-14 7:47 ` Miles Bader
2004-10-09 19:02 ` [rmail-mbox-branch]: mail-utils Stefan
2004-10-11 10:36 ` Simon Josefsson
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=878yafj2tn.fsf@oak.pohoyda.family \
--to=alexander.pohoyda@gmx.net \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 NNTP newsgroup(s).