From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Backend writing
Date: Fri, 03 Aug 2001 23:44:46 +0200 [thread overview]
Message-ID: <iluelqsx1gx.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <vafg0b8kgjm.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 03 Aug 2001 22:57:33 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>| that number, or Gnus will get mightily confused.@footnote{??? Is this
>| still true with the nnchoke-request-*-mark* functions?} Third, article
It's still true.
>| The previous paragraph already mentions all the `hard' restrictions that
>| article numbers must fulfill. But it seems that it might be useful to
>| assign @emph{consecutive} article numbers, for Gnus gets quite confused
>| if there are holes in the article numbering sequence. However, due to
>| the `no-reuse' restriction, holes cannot be avoided altogether.
I would say "is slowed down" instead of "gets quite confused". I
don't think there are any problems, other than that the `gnus-range-*'
functions start to take very long time. Some IMAP servers leave large
holes.
next prev parent reply other threads:[~2001-08-03 21:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 18:04 Sean Rima
2001-08-03 19:24 ` Kai Großjohann
2001-08-03 19:39 ` Paul Jarc
2001-08-03 20:57 ` Kai Großjohann
2001-08-03 21:36 ` Paul Jarc
2001-08-03 22:16 ` Kai Großjohann
2001-08-03 21:44 ` Simon Josefsson [this message]
2001-08-03 22:07 ` Kai Großjohann
2001-08-03 23:35 ` Simon Josefsson
2001-08-03 23:46 ` Paul Jarc
2001-08-04 0:11 ` Simon Josefsson
2001-08-04 0:20 ` Paul Jarc
2001-08-04 0:41 ` Simon Josefsson
2001-08-04 0:57 ` Paul Jarc
2001-08-04 12:36 ` Simon Josefsson
2001-08-05 8:27 ` Paul Jarc
2001-08-03 23:57 ` Paul Jarc
2001-08-04 0:12 ` Simon Josefsson
2001-08-04 0:21 ` Paul Jarc
2001-08-04 11:46 ` Kai Großjohann
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=iluelqsx1gx.fsf@barbar.josefsson.org \
--to=jas@extundo.com \
--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).