From: Pieter Laeremans <pieter@laeremans.org>
Subject: synchronisation between two gnus clients
Date: Sat, 28 Jun 2003 23:59:48 +0200 [thread overview]
Message-ID: <87u1a950dn.fsf@petrus.laeremans.org> (raw)
Hello,
I have to do all my computing work with two computers basicly one at
home and another at my parents home, when I stay there. Neither is
permanently connected to the interent.
I would like though to use gnus on both of them and synchronise it, in
the sense that when I read an article on one of the two I can make
sure it also looks like it's been read on the other.
So I guess I have to always move around some files like .gnus, .newsrc
.newsrc-dribble .
Is that enough to tackle the problem ? I can put those files on a
server and download them when I need them, that 's no problem.
For drafts it seems that I should configure gnus to store them on an
imap server, as for archiving. Then it should be possible to work on
both pc's but let it appear as it is "one gnus" I'm working with.
Any suggestions ? Has anyonen tackled this problem in a
different/better way ?
thanks in advance,
Pieter
P.S. sorry for the bad English
reply other threads:[~2003-06-28 21:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87u1a950dn.fsf@petrus.laeremans.org \
--to=pieter@laeremans.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).