From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: synchronisation of reading same nntp servers from different
Date: Wed, 21 Sep 2005 13:45:58 +0200 [thread overview]
Message-ID: <v9fyrylk3t.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87br2mu20g.fsf@myxomop.com>
On Wed, Sep 21 2005, Alexander Kotelnikov wrote:
>>>>>> On Tue, 20 Sep 2005 14:15:35 +0200
>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
[...]
> SJ> Yes, after using Gnus on one machine, copy ~/News/marks to the other
> SJ> machine. Make sure you call the server the same on the two machines,
> SJ> in the server definition, otherwise you'll have to copy each server
> SJ> directory separately.
>
> Oops... There is no such file or directory in my ~/News/, I use Gnus
> v5.10.7.
nntp marks files are new in No Gnus:
,----[ (info "(gnus)No Gnus") ]
| New features in No Gnus:
|
| [...]
| * The nntp back end store article marks in `~/News/marks'.
|
| The directory can be changed using the (customizable) variable
| `nntp-marks-directory', and marks can be disabled using the (back
| end) variable `nntp-marks-is-evil'. The advantage of this is that
| you can copy `~/News/marks' (using rsync, scp or whatever) to
| another Gnus installation, and it will realize what articles you
| have read and marked. The data in `~/News/marks' has priority
| over the same data in `~/.newsrc.eld'.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-09-21 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 11:45 synchronisation of reading same nntp servers from different machines Alexander Kotelnikov
2005-09-20 12:15 ` Simon Josefsson
2005-09-21 10:51 ` synchronisation of reading same nntp servers from different Alexander Kotelnikov
2005-09-21 11:45 ` Reiner Steib [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=v9fyrylk3t.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).