Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David <de_bb@arcor.de>
To: info-gnus-english@gnu.org
Subject: Re: Synchronizing multiple computers
Date: Tue, 29 Jan 2008 00:32:16 +0100	[thread overview]
Message-ID: <87y7a94jcv.fsf@arcor.de> (raw)
In-Reply-To: <v9tzkxzlb7.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> writes:
> ,----[ (info "(gnus)Various Various") ]
> | `gnus-home-directory'
> |      All Gnus file and directory variables will be initialized from this
> |      variable, which defaults to `~/'.
> `----
>
> ,----[ (info "(message)Various Message Variables") ]
> | `message-directory'
> |      Directory used by many mailey things.  The default is `~/Mail/'.
> |      All other mail file variables are derived from `message-directory'.
> `----

> > | but I guess it does no harm to set them all explicitly.
>
> It's confusing and error-prone, IMHO.

I remember I was confused that there exists 'gnus-home-directory' as
well as 'gnus-directory' where both doc strings more or less say that
everything will be derived from them. I see now that in gnus.el
gnus-directory is set to gnus-home-directory (except when the SAVEDIR
environment variable is set...). In gnus-registry.el,
'gnus-dribble-directory' (which, granted, is usually nil) has precedence
over 'gnus-home-directory' for setting 'gnus-registry-cache-file'. OK, I
suppose I'm nitpicking here...

> | rsync -e "ssh -l name" -auvzp workcomputer:./Gnus ~/.
>
> Only ancient versions of rsync don't use ssh by default. 

OK.

> I'd suggest to get rid of the shell script and do it in elisp[1].

Yes. This setup 'evolved' before I became more familiar with elisp...

> Within Emacs, the values of `gnus-directory', `message-directory',
> `gnus-startup-file', ... are available, you can use them in the sync
> function.  I'd guess that you don't even need to bother about frobbing
> `gnus-home-directory' and `message-directory'.  Just rsync ~/.newsrc*,
> ~/Mail and ~/News.  Or am I missing something?

Since I guess I am only using ~10% of Gnus' functionality I wouldn't
know for sure. I guess syncing the registry file isn't really necessary?

> Nice idea.  Maybe adding a prompt "Do you want to sync from ... to
> ...?" would make sense.

Yes. I'll revise that page as soon as I have time. Thanks for your
comments.

-David

  reply	other threads:[~2008-01-28 23:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 19:46 Martin Geisler
2008-01-28 20:31 ` David
2008-01-28 21:34   ` Reiner Steib
2008-01-28 23:32     ` David [this message]
2008-02-04 23:32     ` David
     [not found]     ` <mailman.6973.1202167981.18990.info-gnus-english@gnu.org>
2008-02-05 15:13       ` Gour
2008-02-10 11:25       ` Gour
2008-02-10 17:31         ` David
2008-01-28 21:37   ` Martin Geisler
2008-01-30 16:44     ` David
2008-01-30 17:40       ` Martin Geisler
     [not found]   ` <mailman.6686.1201630106.18990.info-gnus-english@gnu.org>
2008-01-30 16:04     ` Stefan Monnier
2008-01-30 17:57       ` Martin Geisler
2008-01-31 19:37         ` Reiner Steib
2008-02-01  7:37           ` Martin Geisler
     [not found]           ` <mailman.6834.1201851616.18990.info-gnus-english@gnu.org>
2008-02-01  8:19             ` Gour
     [not found]       ` <mailman.6759.1201715839.18990.info-gnus-english@gnu.org>
2008-01-31 11:50         ` Johan Bockgård
2008-02-01  7:35           ` Martin Geisler

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=87y7a94jcv.fsf@arcor.de \
    --to=de_bb@arcor.de \
    --cc=info-gnus-english@gnu.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).