Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: syncing groups/topics arrangement between machines?
Date: Sun, 03 Jan 2016 17:43:50 -0500	[thread overview]
Message-ID: <87egdywaft.fsf@gmail.com> (raw)
In-Reply-To: <87io3jmlxg.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 28 Dec 2015 08:55:23 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Well, the OP's question indicates otherwise :) Right now .newsrc
> contains quite a bit of information that could be considered user-level
> customizations: which groups are subscribed, group parameters, the topic
> layout, and the highly-confusing `gnus-server-alist'. Values that only
> change when the user explicitly changes them. These things are editable
> through the Gnus interface, but I think users would be a lot happier if
> they were also stored separately, in a format that could be safely
> shared between computers, and maybe even editable by hand.

This is a nice summary of what I have just been looking through gnus
INFO and trying to figure out.

So... many gnus configurations elements can be set either interactively
or through init files (e.g., creating servers and groups). Others can
only be set interactively and saved in .newsrc. I confess, I am having a
hard time keeping clear which is which.

Are any of the "user-level customizations" above also settable in init
files?

Thanks, - George


  reply	other threads:[~2016-01-03 22:43 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
2015-12-28  0:55         ` Eric Abrahamsen
2016-01-03 22:43           ` myglc2 [this message]
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=87egdywaft.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=eric@ericabrahamsen.net \
    --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).