From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: gnus-sync.el v2
Date: Sun, 06 Nov 2011 22:29:22 +0100 [thread overview]
Message-ID: <87zkg92b4d.fsf@dod.no> (raw)
In-Reply-To: <87d3d54bno.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> Actually I can kill those groups. I don't use them anymore (I use my
> squeezeboxen to listen to podcasts at home, and I use rhythmbox to
> download and listen to them on mylaptop).
FWIW, with the troublesome nnrss groups gone from my .newsrc.eld, I
could load the old gnussync file, and save it to lesync database.
So what's left now is to start using it.
Next step in the config, is:
;; - use gnus-after-set-mark-hook and gnus-before-update-mark-hook to
;; catch the mark updates
I guess there are functions that should be added to these hooks, but which
ones? Or am I supposed to write my own functions to add to the hooks?
next prev parent reply other threads:[~2011-11-06 21:29 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 14:20 how do I subscribe to a group as a string from code? Ted Zlatanov
2011-10-20 19:07 ` Tassilo Horn
2011-10-20 19:28 ` Ted Zlatanov
2011-10-20 20:11 ` Tassilo Horn
2011-10-20 21:19 ` Ted Zlatanov
2011-10-21 14:44 ` Steinar Bang
2011-10-24 13:19 ` gnus-sync.el v2 (was: how do I subscribe to a group as a string from code?) Ted Zlatanov
2011-10-24 20:48 ` gnus-sync.el v2 Steinar Bang
2011-10-25 13:02 ` Ted Zlatanov
2011-10-25 15:57 ` Steinar Bang
2011-10-25 16:23 ` Ted Zlatanov
2011-10-25 17:16 ` Steinar Bang
2011-10-25 17:22 ` Steinar Bang
2011-10-25 17:50 ` Ted Zlatanov
2011-10-25 18:10 ` Steinar Bang
2011-10-27 7:28 ` Katsumi Yamaoka
2011-10-27 9:42 ` Steinar Bang
2011-10-27 11:23 ` Steinar Bang
2011-10-27 17:36 ` Ted Zlatanov
2011-10-27 19:40 ` Ted Zlatanov
2011-11-03 21:09 ` Steinar Bang
2011-11-03 21:43 ` Ted Zlatanov
2011-11-03 22:37 ` Steinar Bang
2011-11-04 12:19 ` Ted Zlatanov
2011-11-04 20:52 ` Steinar Bang
2011-11-04 21:18 ` Ted Zlatanov
2011-11-05 7:53 ` Steinar Bang
2011-11-05 9:54 ` Ted Zlatanov
2011-11-05 10:45 ` Steinar Bang
2011-11-05 11:18 ` Steinar Bang
2011-11-05 13:03 ` Ted Zlatanov
2011-11-05 17:54 ` Steinar Bang
2011-11-05 17:59 ` Adam Sjøgren
2011-11-05 18:53 ` Steinar Bang
2011-11-05 13:00 ` Ted Zlatanov
2011-11-05 17:49 ` Steinar Bang
2011-11-05 18:57 ` Steinar Bang
2011-11-05 19:09 ` Steinar Bang
2011-11-05 19:59 ` Steinar Bang
2011-11-05 20:09 ` Adam Sjøgren
2011-11-05 22:13 ` Steinar Bang
2011-11-05 22:35 ` Adam Sjøgren
2011-11-06 13:13 ` Ted Zlatanov
2011-11-06 13:34 ` Steinar Bang
2011-11-06 14:07 ` Ted Zlatanov
2011-11-06 19:23 ` Steinar Bang
2011-11-06 20:49 ` Steinar Bang
2011-11-06 21:29 ` Steinar Bang [this message]
2011-11-07 19:55 ` Steinar Bang
2011-11-07 20:08 ` Steinar Bang
2011-11-09 0:52 ` Ted Zlatanov
2011-11-09 9:27 ` Steinar Bang
2011-11-09 14:17 ` Ted Zlatanov
2011-11-09 0:47 ` Ted Zlatanov
2011-11-09 9:31 ` Steinar Bang
2011-11-09 14:15 ` Ted Zlatanov
2011-11-13 7:51 ` Steinar Bang
2011-11-09 0:45 ` Ted Zlatanov
2011-11-09 9:32 ` Steinar Bang
2011-11-06 7:22 ` Steinar Bang
2011-10-29 19:02 ` Steinar Bang
2011-10-31 17:25 ` Ted Zlatanov
2011-10-25 17:02 ` Steinar Bang
2011-11-03 22:43 ` Lars Magne Ingebrigtsen
2011-11-04 8:09 ` Steinar Bang
2011-11-04 12:20 ` Ted Zlatanov
2012-12-02 10:13 ` Andreas Schwab
2012-12-02 10:19 ` Andreas Schwab
2012-12-02 16:17 ` Ted Zlatanov
2013-01-27 4:27 ` Ted Zlatanov
2013-01-27 6:31 ` Eric S Fraga
2013-01-27 16:35 ` Steinar Bang
2012-12-03 9:50 ` Steinar Bang
2012-12-03 10:30 ` Matt Ford
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=87zkg92b4d.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).