Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: (provide 'nnmaildir)
Date: 15 Jul 2000 02:15:02 +0200	[thread overview]
Message-ID: <ilu4s5sckqh.fsf@barbar.josefsson.org> (raw)
In-Reply-To: Paul Jarc's message of "14 Jul 2000 19:10:18 -0400"

Paul Jarc <prj@po.cwru.edu> writes:

> I've been developing on emacs 20.3 and Gnus 5.6.45.  (Has the
> backend interface changed since then?)

No.

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

If you can make them small and contiguous, do so.  Gnus keeps
(un)compressing ranges and sorting them and stuff, and that is _slow_
even when the highest article number is a few hundred thousand.

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

> The server argument to the backend functions is the second element of
> the select method, right?  A string, typically?  And as the author of
> the backend, I decide what it means?  (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.

> I'm unclear about the usage of nnoo-change-server and
> nnoo-push-server.  I've just been working from (un/sparsely commented)
> examples in the various nn*.el to guess where to use each.  If I
> define a backend variable like (defvoo nnmaildir-maildir "~/Maildir/")
> and use a select method like
> '(nnmaildir "blah" (nnmaildir-maildir "/path/to/maildir")) then my
> understanding is that nnoo-change-server will, among other things, pick
> up the value of nnmaildir-maildir from the defs argument, and that
> value will be visible to nnmaildir-open-server (i.e., the caller of
> nnoo-open-server).  Is this right?

I think so.

>  What about nnoo-push-server?

I don't think you should use it.

> Can I see a concrete example of what a real-life NOV line would look
> like, as written to nntp-server-buffer?

747	(provide 'nnmaildir)	Paul Jarc <prj@po.cwru.edu>	14 Jul 2000 19:10:18 -0400	<m3ya3448bp.fsf@multivac.student.cwru.edu>		5909	85	Xref: barbar.josefsson.org ding:747	

> Can I get away with using article numbers for references there?

I don't think so, they should be taken from the References: header.

> Why does gnus-nov-is-evil exist?

Some NNTP servers are broken wrt NOV.

> How does Gnus know whether a backend supports article identification
> by article number ranges or Message-IDs?  I guess backends must fail
> sensibly if they don't support these, hm?

Gnus doesn't know, so yes, you need to take care of it.  Call
(nnheader-report 'nnmaildir "I don't support message-id fetching") or
something.




  parent reply	other threads:[~2000-07-15  0:15 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 [this message]
2000-07-15  0:51   ` Paul Jarc
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=ilu4s5sckqh.fsf@barbar.josefsson.org \
    --to=simon@josefsson.org \
    --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).