Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: nnmaildir & expiry (again..)
Date: Mon, 27 Sep 2004 11:16:42 -0400	[thread overview]
Message-ID: <m3wtyfbv2n.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <86fz575xff.fsf@ID-110038.user.uni-berlin.de> =?iso-8859-1?Q?=28Rapha=EBl?= Berbain's message of "Sun, 26 Sep 2004 12:52:43 +0200")

raphael.berbain@free.fr (Raphaël Berbain) wrote:
> nnmaildir stores marks quite unusually compared to other
> maildir-aware MUA.  It uses files in
> <maildir>/.nnmaildir/marks/<mark>/file.  Others tend to use the info
> part of the message filename.

Yes.  Having marks as separate files is more concurrency-friendly, for
programs that all use this scheme (right now, that just means
concurrent Gnusae): when one program alters one piece of information
(say, a mark), it does not make it harder for another program to find
another piece of information (say, the message contents).  I posted
this idea to one of DJB's lists, but didn't get much response.

> The only reason I could think of is that Gnus has more marks than
> some other MUAs/imap servers

There's that too.

> I think I once heard about a script (perl, IIRC) that did some kind
> of sync between both systems, but I can't find it again.

<URL:http://multivac.cwru.edu./prj/marksync>


paul



  reply	other threads:[~2004-09-27 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 10:00 Raphaël Berbain
2004-09-24 14:06 ` Paul Jarc
2004-09-26 10:52   ` Raphaël Berbain
2004-09-27 15:16     ` Paul Jarc [this message]
2004-09-28 16:51       ` Raphaël Berbain

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=m3wtyfbv2n.fsf@multivac.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).