all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: dhruva <dhruvakm@gmail.com>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: About mailing lists & digest mails: MIME mails from emacs mailing lists
Date: Thu, 16 Sep 2010 12:56:05 +0900	[thread overview]
Message-ID: <87fwxaz6i2.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <AANLkTimsgPDi7FuiRfPHVK9R_tX90eAggcVtyFSg7MzA@mail.gmail.com>

dhruva writes:

 >  I subscribe to digest mails on emacs-devel list. Though I use MIME
 > format, I do not get topics in the digest mail with hyperlinks to
 > jump to that topic in the mail.

That's right.  Mailman uses plain or MIME digests, not HTML digests.
Please followup to mailman-developers@python.org, preferably with a
patch.

Rationale:

It would not be that hard to add to Mailman an HTML digest generator
that could be used by a text-only list like emacs-devel, and a
per-user option to enable it.  But I doubt that any of the usual
suspects will volunteer to do so, because it would not be generally
useful.  Rather, most people would want it to work with all kinds of
mail in the digest, and that would be a lot of work to do at all, and
very hard to do acceptably well.

OTOH, a MIME digest is simply a sequence of RFC 822 message parts, so
navigation is trivial.  It should be left to the MUA.  A decent MUA
will offer you at least the options of (1) "exploding" the digest so
that the messages are integrated with existing threads in your inbox,
or (2) reading the digest as a folder.




      parent reply	other threads:[~2010-09-16  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16  3:08 About mailing lists & digest mails: MIME mails from emacs mailing lists dhruva
2010-09-16  3:55 ` Glenn Morris
2010-09-16  3:56 ` Stephen J. Turnbull [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=87fwxaz6i2.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=dhruvakm@gmail.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.