Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: r_letot@yahoo.com (Rémi Letot)
Subject: nnmaildir now has persistent article numbers
Date: Mon, 23 Sep 2002 14:46:42 -0400	[thread overview]
Message-ID: <m37khco85z.fsf@multivac.cwru.edu> (raw)

And it's (somewhat) concurrency-friendly, too: you can run two Gnusae
running nnmaildir-request-scan on the same maildir at the same time,
and they won't assign the same article number to two different
messages.  In the spirit of maildir, this is done without needing file
locks.  (However, it could happen that a single message gets two
numbers assigned to it.  Only one number will be stored in the
maildir, but the two Gnusae will disagree for as long as they re both
running.  So don't do that after all.)

Article numbers are stored in .nnmaildir/nov/*.  So caching and
agentizing should work now.  In the past, you could remove the
.nnmaildir/nov/... file to force regeneration of NOV data (although it
should always happen automatically when needed).  Beware that this
will now also cause the message to get a new article number - unless
you do it while Gnus is running and do M-g on the group afterwards, in
which case the old number will be remembered and stored back in the
new NOV file.


paul



             reply	other threads:[~2002-09-23 18:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 18:46 Paul Jarc [this message]
2002-09-23 19:23 ` Josh Huber
2002-09-23 19:33   ` Paul Jarc
2002-09-24 17:41     ` Josh Huber
2002-09-24 18:30       ` Paul Jarc
2002-09-24 20:16         ` Josh Huber
2002-09-24 20:23           ` Paul Jarc
2002-09-24 20:37             ` Josh Huber
2002-09-24 21:11               ` Paul Jarc
2002-09-24 22:32                 ` Josh Huber
2002-09-25 16:04                   ` Paul Jarc
2002-09-25 17:23                     ` Paul Jarc
2002-09-25 23:35                     ` Josh Huber
2002-09-26 16:18                       ` Paul Jarc
2002-09-26 17:39                         ` Josh Huber
2002-09-25 13:48           ` 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=m37khco85z.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --cc=r_letot@yahoo.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).