Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: adding a new digest type to nndoc-type-alist
Date: 26 Sep 2000 00:19:45 +0200	[thread overview]
Message-ID: <vafn1gw15dq.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Ted Stern's message of "25 Sep 2000 11:04:10 -0700"

On 25 Sep 2000, Ted Stern wrote:

> I recently subscribed to a mailing list on eGroups and elected to
> receive notices in digested form.  The individual messages are
> separated by double lines of underscores, which seems like a good
> convention, unlikely to be found in ordinary emails.

The problem is the header formatting.  You'd need to include a
function which removes the spaces before header names.

Sadly, I've never written a function like this, but it seems that
there are a couple of `generate-head-function' examples in the default
value that one could look at.

kai
-- 
I like BOTH kinds of music.



      reply	other threads:[~2000-09-25 22:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-25 18:04 Ted Stern
2000-09-25 22:19 ` Kai Großjohann [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=vafn1gw15dq.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.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).