Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: syncing groups/topics arrangement between machines?
Date: Sun, 27 Dec 2015 22:05:54 +0100	[thread overview]
Message-ID: <87twn3lhzh.fsf@debian.uxu> (raw)
In-Reply-To: <87r3i8mn8a.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> It's kept in the variable `gnus-topic-alist', which
> is saved to the file pointed to by
> `gnus-startup-file', which on this machine points to
> ~/.emacs.d/.newsrc. That's where gnus stores most of
> its state, including subscribed groups and
> message marks.
>
> I wouldn't recommend copying this file between
> machines -- I tried that before, and it didn't work
> out well.

How so?

If Gnus stores its state there and the state is
identical the result should be identical. If it isn't,
something is wrong.

I'll try it right now and tell you how it went...

> There is a possibility that in the future, Gnus'
> various state objects will be separated out a little
> more cleanly. It would be nice to at least have
> a separation between "settings than can be synced or
> kept in version control" (which would include group
> subscriptions and topic arrangements), and "settings
> that only Gnus should mess with", which I guess
> would mostly be marks.

Yeah, but isn't that separation exactly what is with
.gnus and .newsrc[.eld]?

-- 
underground experts united
http://user.it.uu.se/~embe8573



  parent reply	other threads:[~2015-12-27 21:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27  5:12 Benjamin Slade
2015-12-27  5:34 ` Emanuel Berg
2015-12-27  5:47   ` Benjamin Slade
2015-12-27  6:15     ` Eric Abrahamsen
2015-12-27  6:45       ` Benjamin Slade
2015-12-27  7:17         ` Eric Abrahamsen
2015-12-27 21:05       ` Emanuel Berg [this message]
2015-12-28  0:55         ` Eric Abrahamsen
2016-01-03 22:43           ` myglc2
2016-01-04  1:33             ` Eric Abrahamsen
2015-12-28  5:37         ` Benjamin Slade
2015-12-28 16:46         ` Benjamin Slade

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=87twn3lhzh.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).