From: Rob Browning <rlb@cs.utexas.edu>
Cc: ding@gnus.org
Subject: Re: "Fixing up" gnus - (how hard is this?).
Date: 17 Oct 2000 17:53:29 -0500 [thread overview]
Message-ID: <87wvf7m652.fsf@raven.localnet> (raw)
In-Reply-To: prj@po.cwru.edu's message of "17 Oct 2000 16:29:11 -0400"
prj@po.cwru.edu (Paul Jarc) writes:
> nnmaildir writes its state file frequently, but it is one monolithic
> file per group. I may move to some form of journaling, but I've got
> other changes to get to first.
One simple thing to do is to always write the state file to a temp
file then do the link/unlink trick to make sure there's always a
coherent copy of the file in place. This fixes corruption problems,
but not data-lossage.
> User-defined, you mean? That would be useful indeed. Obviously, it
> requires cooperation from Gnus, though.
Absolutely. I tend to feel that gnus' current set of marks is sorta
ad-hoc when considered in the mail context. While I like the idea of
using the same tool for mail and news, I think that mail does have
some special semantics that ought to be more explicitly accomodated,
and well documented.
Thanks for the responses.
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
next prev parent reply other threads:[~2000-10-17 22:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 16:00 "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir)) Rob Browning
2000-10-17 20:29 ` "Fixing up" gnus - (how hard is this?) Paul Jarc
2000-10-17 22:53 ` Rob Browning [this message]
2000-10-17 20:51 ` "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir)) Simon Josefsson
2000-10-17 22:32 ` Rob Browning
2000-10-18 15:13 ` Paul Jarc
2000-10-18 20:07 ` Rob Browning
2000-10-18 20:29 ` Paul Jarc
2000-10-19 0:20 ` Rob Browning
2000-10-19 16:05 ` Paul Jarc
2000-10-19 23:29 ` Rob Browning
2000-10-20 0:03 ` Paul Jarc
2000-10-20 9:21 ` Kai Großjohann
2000-10-20 15:27 ` Paul Jarc
2000-10-20 21:08 ` Kai Großjohann
2000-10-20 21:17 ` Paul Jarc
2000-10-20 21:45 ` 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=87wvf7m652.fsf@raven.localnet \
--to=rlb@cs.utexas.edu \
--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).