From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Gnus and resilience to datafile corruption...
Date: Sat, 04 May 2002 19:58:15 -0400 [thread overview]
Message-ID: <m3helna2j6.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87n0vg1om6.fsf@enki.rimspace.net> (Daniel Pittman's message of "Sat, 04 May 2002 15:14:09 +1000")
Daniel Pittman <daniel@rimspace.net> wrote:
> It would seem reasonable to create a .properties file, similar to the
> .marks, that stored individual group properties in the nnml groups.
This could be done, sort of, but not very well without an enhancement
to the backend interface. Backends can update Gnus's copy of the
group parameters, but backends aren't ever notified when the user
changes parameters a la -request-set-mark for marks, so they can't
tell whether their copy or Gnus's copy is more up to date.
> * nntp group marks and properties
>
> These are only stored in the .newsrc.eld file, resulting in my losing
> all the information about them. WIBNI they were stored in the nnml
> redundant and split style somewhere?
If you want redundancy, keep backups. Duplicating information storage
is pointless when Gnus has no way of knowing that one form of storage
is more reliable than another. It's just one more thing that can
break.
Note that you can specify all your group properties in the
gnus-parameters variable, if your .gnus is more reliable than your
.newsrc.eld.
paul
next prev parent reply other threads:[~2002-05-04 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 5:14 Daniel Pittman
2002-05-04 23:58 ` Paul Jarc [this message]
2002-05-05 2:04 ` Daniel Pittman
2002-05-05 21:55 ` Paul Jarc
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=m3helna2j6.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).