Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@buug.org>
To: info-gnus-english@gnu.org
Subject: Group parameters
Date: Fri, 31 Aug 2012 05:02:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120831T063928-708@post.gmane.org> (raw)

I have Gnus installed on 2 computers ("desktop" and "laptop").  I would
like my groups to have exactly the same parameters in both cases.  It
doesn't have to be completely automatic, but not completely manual,
either; that is, I want to avoid doing G c on each group on each
computer and entering the same things.  The shape of the solution I have
in mind is that after customizing a group on one computer I execute a
magic command foo (inside Emacs or otherwise) and the changes propagate
to the other.  (This is how I handle many other situations, with foo ==
unison).

However, the way Gnus saves the group parameters unfortunately doesn't
easily allow such solution: it saves them into the newsrc.eld file along
with, and interspersed with, other data that is clearly instance
specific, so I cannot just sync the whole file.  I guess I could use the
gnus-parameters variable and read it from a different file, maybe
.emacs.  But that still has 2 big disadvantages: 1. I am condemned to
use plain Lisp to set the parameters instead of Customize, and 2. I
cannot see a way to export the parameters I have already accumulated so I
would have to start by translating them manually (for each group).

Presumably 2 can be solved with some personal Lisp code, but 1 would
remain.  Does anyone have a helpful idea?

             reply	other threads:[~2012-08-31  5:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  5:02 Ian Zimmerman [this message]
2012-08-31  6:30 ` Kevin Brubeck Unhammer
2012-08-31 14:21   ` William Gardella

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=loom.20120831T063928-708@post.gmane.org \
    --to=itz@buug.org \
    --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).