From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Gnus and resilience to datafile corruption...
Date: Sun, 05 May 2002 17:55:15 -0400 [thread overview]
Message-ID: <m3offu9s4m.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87k7qjnyd4.fsf@enki.rimspace.net> (Daniel Pittman's message of "Sun, 05 May 2002 12:04:55 +1000")
Daniel Pittman <daniel@rimspace.net> wrote:
> It would require extending the interface to support a nnfoo
> `-request-set-properties' method, then call that on the backend when
> it's implemented.
>
> That should be backward compatible, yes?
Right.
>> If you want redundancy, keep backups.
>
> I do, but not quite so up to date as the application specific ones that
> NNML maintains. :)
(add-hook 'gnus-save-newsrc-hook
(lambda ()
(copy-file "~/.newsrc.eld" "~/.newsrc.eld.backup" 'ok-if-already-exists)))
Or split it up among several files, if you like.
> In the end I wouldn't care if .newsrc.eld didn't exist
I think that's a popular goal.
paul
prev parent reply other threads:[~2002-05-05 21:55 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
2002-05-05 2:04 ` Daniel Pittman
2002-05-05 21:55 ` Paul Jarc [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=m3offu9s4m.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).