Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: which gnus files used to hold gnus state? (for manual)
Date: Tue, 20 May 2003 14:10:32 -0400	[thread overview]
Message-ID: <4nznlhcwvb.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <84d6iin27t.fsf@lucy.is.informatik.uni-duisburg.de> ( =?iso-8859-1?q?Kai_Gro=DFjohann's_message_of?= "Fri, 16 May 2003 21:03:34 +0200")

On Fri, 16 May 2003, kai.grossjohann@gmx.net wrote:
> John Owens <jowens@ece.ucdavis.edu> writes:
> 
>> I'd like to get a list of the files used to hold gnus state. This
>> is for potential inclusion in the manual (after discussion with
>> Lars) and would be important for users who are interested in
>> synching the gnus state of two machines (say, a laptop and a
>> desktop).
> 
> There is also gnus-registry.el which comes into play.  But maybe Ted
> should say something about it.

The registry basically stores data that would normally go into the
newrs.eld file, into ~/.gnus.registry.eld.  You have to enable and
load the gnus-registry.el package, though.  Also, a missing/corrupted
registry would not impact anything, except send articles to the
default/wrong mailbox with parent splitting, or register messages as
spam or ham incorrectly or not at all.  So synchronization of the
registry, as it's used now and as it will be used in my plans, is not
necessary to preserve the state of Gnus.

Ted



      parent reply	other threads:[~2003-05-20 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  5:54 John Owens
2003-05-16 19:03 ` Kai Großjohann
2003-05-16 20:50   ` Andreas Fuchs
2003-05-16 21:43   ` Kevin Greiner
2003-05-17 17:12     ` Kai Großjohann
2003-05-20 18:10   ` Ted Zlatanov [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=4nznlhcwvb.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.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).