From: Vegard Vesterheim <vegard.vesterheim@uninett.no>
To: ding@gnus.org
Subject: Re: elp-wrapper sneaking into .newsrc.eld
Date: Mon, 06 Dec 2010 10:33:50 +0100 [thread overview]
Message-ID: <1sr5dvp7nl.fsf@voll.uninett.no> (raw)
In-Reply-To: <yb0fwubuwt5.fsf@dod.no> (Steinar Bang's message of "Mon, 06 Dec 2010 09:31:34 +0100")
On Mon, 06 Dec 2010 09:31:34 +0100 Steinar Bang <sb@dod.no> wrote:
> In my opinion, the .newsrc.eld should be split up.
>
> Lars always asks "why?" when I suggest this. The answers are:
> - It's a big file that's fragile wrt. to small obscure changes (it's
> better to lose tick marks in one group, than in all of them)
> - I would like to have my manually edited stuff (group parameters, and
> servers, and perhaps other stuff) out of .newsrc.eld and into a file,
> or set of files, that can be version controlled and shared together
> with the rest of the configuration files in my home directory
>
> (I think there are other reasons as well, but these are the ones that
> came to mind right now)
Another reason is to simplify the process of using separate Gnusae
(across several computers/user accounts) for IMAP. Other IMAP clients
only needs the connection details for the IMAP server, and will fetch
the rest of the information from the server.
To bootstrap a new Gnus, you need to take several steps
- configure your .authinfo.gpg file for credentials
- configure the TLS mechanism (starttls, gnutls ...)
- configure select methods in .gnus
- copy your ~/.newrc.eld
- copy some directories (~/News etc)
I would love to see a simpler mechanism for getting Gnus running on a
new user account. There has been some ideas floating around about
storing some info on the IMAP server (using IMAP as a file storage with
tramp), but I am not sure how well this works in practise. Can anyone
share any details about how to do this?
Yes, I know that Gnus is not just an IMAP-server. It is for me.
Yes, I know there is a potential chicken-and-egg problem here about
bootstrapping Gnus using information from IMAP.
- Vegard V -
next prev parent reply other threads:[~2010-12-06 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 21:44 Dan Christensen
2010-12-05 21:52 ` Lars Magne Ingebrigtsen
2010-12-05 22:00 ` Dan Christensen
2010-12-05 22:38 ` Lars Magne Ingebrigtsen
2010-12-05 23:28 ` Dan Christensen
2010-12-06 8:31 ` Steinar Bang
2010-12-06 9:33 ` Vegard Vesterheim [this message]
2010-12-06 13:29 ` Lars Magne Ingebrigtsen
2010-12-06 20:56 ` Steinar Bang
2010-12-15 16:34 ` Ted Zlatanov
2010-12-15 19:41 ` Steinar Bang
2010-12-15 20:59 ` Ted Zlatanov
2010-12-06 13:31 ` Lars Magne Ingebrigtsen
2010-12-06 21:01 ` Steinar Bang
2010-12-15 16:36 ` Ted Zlatanov
2010-12-15 19:11 ` Lars Magne Ingebrigtsen
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=1sr5dvp7nl.fsf@voll.uninett.no \
--to=vegard.vesterheim@uninett.no \
--cc=ding@gnus.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).