Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: User defined digest types in Gnus
Date: 04 Mar 1996 20:38:20 +0100	[thread overview]
Message-ID: <x668ck1xp2.fsf@eyesore.no> (raw)
In-Reply-To: abraham@dina.kvl.dk's message of 04 Mar 1996 16:10:49 +0100

abraham@dina.kvl.dk (Per Abrahamsen) writes:

> For situations like this, it would be nice if there was a well
> documented way to add new digest types to Gnus.
> 
> `nndoc-type-alist' almost provides this, with two exceptions:
> 
> 1) It should be documented (although it seems pretty straight-forward).
> 
> 2) Each digest type description should contain a function that returns
> non-nil if the current buffer is a digest of that type.  This would
> avoid the hard-coding of the digest types in `nndoc-guess-digest-type'. 

Yup.  I've now added this to the Red Gnus todo list.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-03-04 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-04 15:10 Per Abrahamsen
1996-03-04 19:38 ` Lars Magne Ingebrigtsen [this message]
1996-03-04 20:24 ` Edward J. Sabol

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=x668ck1xp2.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).