Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: (provide 'nnmaildir)
Date: Fri, 14 Jul 2000 20:51:42 -0400 (EDT)	[thread overview]
Message-ID: <20000715005142.7982.qmail@multivac.student.cwru.edu> (raw)
In-Reply-To: <ilu4s5sckqh.fsf@barbar.josefsson.org>

Simon Josefsson writes:
> Paul Jarc <prj@po.cwru.edu> writes:
> > So... what conditions are article numbers supposed to satisfy?
> 
> They must be a positive elisp integer, and article numbers should be
> persistant between gnus sessions.

So an article number for a particluar message must be constant for the
life of that message... after a message expires, can its article
number be reused?  My experiments indicate that nothing breaks
violently, but Gnus remembers the readness of the article even after
it expires, so a new article using the same number won't show up as
new. :(  It'd be nice if Gnus didn't mark numbers as read when they
have no article and are less than the number of a truly read article.

> > What do NNTP servers do when they run out (I'm assuming they don't
> > use bignums), and how does Gnus react?
> 
> Gnus just barf at article numbers > 2^28.

Ok... but do actual NNTP servers count into infinity?  They never
shift article numbers back to make room; do they ever wrap around to 0
(or 1)?  I would have thought that there must be a server out there
that's been in operation long enough to hit 2^32... or at least that
the authors of NNTP servers would take it into consideration.

> > (Right now, I'm using it to specify the path to the maildir, but I
> > think I'll create a backend variable for that purpose instead.)
> 
> Yes.  A good idea for the variable name would be `nnmaildir-directory'
> to match nnml etc.

Check, wilco.

> >  What about nnoo-push-server?
> 
> I don't think you should use it.

What I saw in other backends was that nnoo-change-server was used in
*-open-server, and nnoo-push-server was used everywhere else.  Should
I use nnoo-change-server in all cases?  What about backend functions
that don't take a defs argument?  How will they get the proper values
of the backend variables for the current server?  Or is *-open-server
always called first, if necessary, to make a server be current before
calling another backend function?

> > Can I get away with using article numbers for references there?
> 
> I don't think so, they should be taken from the References: header.

Yes, but what does Gnus do with them?  Construct threads, yes?  Is
this done is such a way that article numbers would work as well?  Or:
could Gnus be *made* to allow this? ;)  If I can keep article numbers
small, and if I can use them for References, then encoding NOV lines
in filenames might be feasible.

> > Why does gnus-nov-is-evil exist?
> 
> Some NNTP servers are broken wrt NOV.

So if my non-NNTP backend isn't broken, must I still obey it?

Since my last message, I've found more threads about maildir in the
archive (and haven't checked gnu.emacs.gnus yet), so I may yet
discover that this is a solved problem... particularly, I get the
impression there's some support in Pterodactyl Gnus.  I don't know yet
if it's just treating a maildir as an inbox, or if it's actually
*using* a maildir.


paul



  reply	other threads:[~2000-07-15  0:51 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 23:10 Paul Jarc
2000-07-14 23:47 ` Steve Harris
2000-07-15  0:56   ` Paul Jarc
2000-07-16  1:14     ` Steve Harris
2000-07-16 12:44       ` Simon Josefsson
2000-07-17  2:43         ` Steve Harris
2000-07-17 18:28           ` Paul Jarc
2000-07-18  9:04             ` Kai Großjohann
2000-07-18 10:16             ` Simon Josefsson
2000-07-18 15:34               ` Steve Harris
2000-07-18 16:34                 ` Simon Josefsson
2000-07-18 16:48                   ` Kai Großjohann
2000-07-19 15:36                   ` Steve Harris
2000-07-20 14:19                     ` Paul Jarc
2000-07-24 20:10                       ` Paul Jarc
     [not found]                         ` <vafittodfig.fsf@lucy.cs.uni-dortmund.de>
2000-07-31 16:42                           ` Paul Jarc
2000-08-01 16:03                             ` Paul Jarc
2000-08-02 14:51                               ` Paul Jarc
2000-08-03 14:58                                 ` Paul Jarc
2000-08-04 15:44                                   ` Paul Jarc
2000-08-07 22:35                                     ` Paul Jarc
2000-08-11 15:01                                     ` Paul Jarc
2000-08-11 21:07                                       ` Kai Großjohann
2000-08-11 21:34                                         ` Paul Jarc
2000-08-13 16:08                                           ` Kai Großjohann
2000-09-04  3:51                                       ` Paul Jarc
2000-09-04  4:20                                         ` Paul Jarc
2000-09-04  8:26                                         ` Simon Josefsson
2000-09-05 18:49                                           ` Paul Jarc
2000-09-21 17:30                                         ` Paul Jarc
2000-09-21 21:30                                           ` Kai Großjohann
2000-09-21 22:43                                             ` Paul Jarc
2000-07-15  0:15 ` Simon Josefsson
2000-07-15  0:51   ` Paul Jarc [this message]
2000-07-15  1:21     ` Simon Josefsson
2000-07-15  1:24     ` Russ Allbery
2000-07-15 11:45     ` Kai Großjohann
2000-07-15 13:12       ` Simon Josefsson
2000-07-15 11:43 ` Kai Großjohann
2000-07-16 21:34   ` Paul Jarc
2000-07-16 21:47     ` Kai Großjohann
2000-07-17 18:17       ` Paul Jarc
2000-09-28 16:05 ` Paul Jarc
2000-09-28 18:46   ` Paul Jarc
2000-10-04 18:06 ` Paul Jarc
2000-10-04 18:21   ` Paul Jarc
2000-10-04 19:31     ` Simon Josefsson
2000-10-04 19:34       ` Paul Jarc
2000-10-04 19:52         ` Simon Josefsson
2000-10-04 20:32           ` Paul Jarc
2000-10-05  8:57             ` Simon Josefsson
2001-04-11 16:10 ` Paul Jarc
2001-04-15  3:57 ` Paul Jarc
2001-04-17  0:55 ` Paul Jarc
2001-04-24 15:11 ` Paul Jarc
2001-04-25 13:42   ` Paul Jarc

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=20000715005142.7982.qmail@multivac.student.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).