Gnus development mailing list
 help / color / mirror / Atom feed
From: Jason R Mastaler <jason@mastaler.com>
Subject: Re: TODO idea:
Date: 10 Jun 1997 21:49:35 -0600	[thread overview]
Message-ID: <x7pvttol2o.fsf@mastaler.com> (raw)
In-Reply-To: Wesley Hardaker's message of "10 Jun 1997 08:58:53 +0200"

Wesley Hardaker <whardake@sphysdec1.unil.ch> writes:

> Well, that was the original idea technically...  nnml can be
> considered nnmh really...  its just better, as nnmh doesn't keep
> records of things.  Anyway, It should be a new interface as not
> everyone wants to create the new file, there for it should be a
> super-class (what is the oo stuff called in nnoo?) of nnml...  But I
> definately do want it in nnml, not nnmh, as its a better interface for
> gnus...

Not keeping records of some things (like an active file) can sometimes
be useful.  I specifically use nnmh so I can read all my mail outside
Gnus if I want.  Back to the issue of a new backend.  Being ignorant
of the design issues involved, I'll ask why not just give the user the
choice of adding the unseen sequences file functionality to the
current backend(s) if she wants to use it? (extra option or something)
-- it seems like it would more flexible that way. 

And yes I agree, for *Gnus*, nnml is a better interface.

   Jason R. Mastaler                      jason@mastaler.com


  reply	other threads:[~1997-06-11  3:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-06  7:00 Wesley Hardaker
1997-06-06  9:29 ` Lars Balker Rasmussen
1997-06-06 11:28   ` Kai Grossjohann
1997-06-06 17:36 ` Lars Magne Ingebrigtsen
1997-06-09  8:39   ` Wesley Hardaker
1997-06-10  2:58     ` Jason R Mastaler
1997-06-10  6:58       ` Wesley Hardaker
1997-06-11  3:49         ` Jason R Mastaler [this message]
1997-06-11  6:49           ` Wesley Hardaker
1997-06-16 18:10           ` Paul Graham
1997-06-17 15:34             ` Lars Magne Ingebrigtsen
1997-06-18  6:58               ` Wesley Hardaker
1997-06-18 12:09                 ` Lars Magne Ingebrigtsen
1997-06-18 14:55                   ` David S. Goldberg
1997-06-19  8:47                   ` Wesley Hardaker
1997-06-19 17:37                     ` Paul Franklin
1997-06-20  3:58                       ` Darren/Torin/Who Ever...
1997-06-19 18:32                     ` Scott Blachowicz
1997-06-20  9:12                       ` Wesley Hardaker
1997-06-20 18:16                         ` Scott Blachowicz
1997-06-20 21:32                           ` Richard Coleman
1997-06-20 22:12                     ` Lars Magne Ingebrigtsen
1997-06-21  0:08                       ` Richard Coleman
1997-06-21 20:29                         ` Scott Blachowicz
1997-06-22 13:32                         ` Lars Magne Ingebrigtsen
1997-06-22 22:24                           ` Richard Coleman
1997-06-24 21:11                             ` Jason R Mastaler
1997-06-22 23:35                       ` Darren/Torin/Who Ever...
1997-06-17 15:33           ` Lars Magne Ingebrigtsen
1997-06-25  8:34         ` anonymous
1997-06-25 20:26           ` Paul Franklin
1997-06-26  9:38         ` anonymous
     [not found]         ` <1997 <19970626093841.17915.qmail@sunsite.auc.dk>
1997-06-26 19:27           ` Paul Graham
1997-06-26 20:40             ` Paul Franklin
1997-06-10 17:52       ` Paul Franklin

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=x7pvttol2o.fsf@mastaler.com \
    --to=jason@mastaler.com \
    /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).