Gnus development mailing list
 help / color / mirror / Atom feed
From: "Edward J. Sabol" <sabol@thuban.gsfc.nasa.gov>
Subject: Re: User defined digest types in Gnus
Date: Mon, 4 Mar 1996 15:24:43 -0500	[thread overview]
Message-ID: <199603042024.PAA04012@thuban.gsfc.nasa.gov> (raw)
In-Reply-To: <rjhgw4c2rq.fsf@ssv4.dina.kvl.dk> (abraham@dina.kvl.dk)

Excerpts from mail: (04-Mar-96) User defined digest types in Gnus by Per Abrahamsen
> There is some weird format digests in `rec.arts.sf.tv.babylon-5.info'
> that I would like to split. I don't think Gnus should support these by
> default, as they are probably only of interest to Babylon 5 fans.

Yeah, I've come across non-standard digest formats fairly often myself. In
the past, I've usually ended up modifying the source code...

> 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'.

Wow, this is a great idea and long overdue. Maybe we can classify this as a
bug and sneak it into September Gnus rather than waiting for Red?

Later,
Ed


      parent reply	other threads:[~1996-03-04 20:24 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
1996-03-04 20:24 ` Edward J. Sabol [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=199603042024.PAA04012@thuban.gsfc.nasa.gov \
    --to=sabol@thuban.gsfc.nasa.gov \
    /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).