From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: Generating article numbers in new backends
Date: Thu, 01 Aug 2013 14:19:32 +0200 [thread overview]
Message-ID: <m3wqo5li23.fsf@stories.gnus.org> (raw)
In-Reply-To: <7b005d25-7d36-4143-82d4-1d135b58ef0d@googlegroups.com>
pedro.alex.silva@gmail.com writes:
> Is the above harmless and can I just use these SQL IDs for article
> numbers?
It's harmless, but will lead to Gnus overestimating the number of
articles in the group. You can avoid this by using `unexist' tracking.
See nnimap for how it does this.
> If not, what is the best practice for generating Gnus-specific
> article numbers? I've not been able to find documentation on any helper
> functions for this. I perused nnimap and nnrss's source, but it's been
> of no help.
>
> Must I keep a local mapping of SQL IDs to Gnus article numbers?
If you want consecutive numbers in Gnus, I think you do.
--
(domestic pets only, the antidote for overdose, milk.)
No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
prev parent reply other threads:[~2013-08-01 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 22:50 pedro.alex.silva
2013-08-01 12:19 ` Lars Magne Ingebrigtsen [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=m3wqo5li23.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@gnu.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).