From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: elp-wrapper sneaking into .newsrc.eld
Date: Mon, 06 Dec 2010 21:56:29 +0100 [thread overview]
Message-ID: <8739qay60y.fsf@dod.no> (raw)
In-Reply-To: <1sr5dvp7nl.fsf@voll.uninett.no>
>>>>> Vegard Vesterheim <vegard.vesterheim@uninett.no>:
> 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 use Ted's gnus-sync.el (which is in git gnus).
Here's my setup, from .gnus.el:
At the start of the file I've got this (I don't know if it was required
to have it at the start of the file, or if I just put it there so I
would remember to remove it at a later stage):
(require 'gnus-sync)
Further down in the file, I've got this:
;; Synching reads in nntp groups across machines
(setq gnus-sync-backend "/ssh:myuser@hjemme.mydomain:News/gnussync" ; will use Tramp+EPA if loaded
gnus-sync-global-vars `(gnus-newsrc-last-checked-date)
gnus-sync-newsrc-groups `("nntp" "nnrss")
gnus-sync-newsrc-vars `(read marks))
I decided to use tramp+ssh instead of tramp+imap, which is a decision I
now regret.
next prev parent reply other threads:[~2010-12-06 20:56 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
2010-12-06 13:29 ` Lars Magne Ingebrigtsen
2010-12-06 20:56 ` Steinar Bang [this message]
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=8739qay60y.fsf@dod.no \
--to=sb@dod.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).