From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Digest configuration Date: Thu, 13 Sep 2012 20:09:34 +0800 Message-ID: References: Reply-To: jamshark70@dewdrop-world.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7bdc8fb637c36404c9942e3a Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TC8En-00061h-7i for emacs-orgmode@gnu.org; Thu, 13 Sep 2012 08:09:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TC8Eh-0001Mm-Er for emacs-orgmode@gnu.org; Thu, 13 Sep 2012 08:09:41 -0400 Received: from mail-vc0-f169.google.com ([209.85.220.169]:43600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TC8Eh-0001Mg-7M for emacs-orgmode@gnu.org; Thu, 13 Sep 2012 08:09:35 -0400 Received: by vcbfl17 with SMTP id fl17so638033vcb.0 for ; Thu, 13 Sep 2012 05:09:34 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --047d7bdc8fb637c36404c9942e3a Content-Type: text/plain; charset=ISO-8859-1 If there is a very long message, the digest gets truncated. For instance, in digest volume 79, issue 14, the fourth message consists of an immense stack trace. The digest cuts off midway through. According to the table of contents, that leaves 39 messages that I can't read without clicking around in the archives... of course, I take digest delivery to avoid having to do that. There must be a smarter way to group messages into digests so that no single digest is too big, while messages don't get lost. hjh --047d7bdc8fb637c36404c9942e3a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

If there is a very long message, the digest gets truncated. = For instance, in digest volume 79, issue 14, the fourth message consists of= an immense stack trace. The digest cuts off midway through. According to t= he table of contents, that leaves 39 messages that I can't read without= clicking around in the archives... of course, I take digest delivery to av= oid having to do that.

There must be a smarter way to group messages into digests s= o that no single digest is too big, while messages don't get lost.

hjh

--047d7bdc8fb637c36404c9942e3a--