Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Syncing gmane group read state across multiple gnusen
Date: Fri, 19 Jun 2009 17:41:25 +0200	[thread overview]
Message-ID: <m37hz8mdsq.fsf_-_@dod.no> (raw)
In-Reply-To: <87d490o171.fsf@uninett.no>

>>>>> Vegard Vesterheim <vegard.vesterheim@uninett.no>:

> Hmm, maybe this initial visiting of all imap groups (to resync unread
> counts) can be scripted/automated via elisp? That would at least
> alleviate the problem somewhat.

Should be doable.

I've also wanted to do something similar, but more advanced, on Gmane
groups:
 - visit the group
 - walk through all unread articles, and visit them, and then
  - if present, mark as unread and go to the next article
  - if expired (typically reported spam articles), skip to the next
    article 

What's kept me from doing it so far, is that the function for visiting
articles, seemed not very appropriate to run as a lisp function (can't
remember why or what, only that it wasn't obvious how I should use it).

Also, since this
 ;; Store article in agent when reading it while online
 (add-hook 'gnus-select-article-hook 'gnus-agent-fetch-selected-article)
no longer works to cache all read articles in agent, the nice side
effect of having cached _all_ articles in in a group, not just the ones
smaller than whatever cutoff size, isn't present




  reply	other threads:[~2009-06-19 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  8:45 Steinar Bang
2009-06-18 10:24 ` Duncan
2009-06-18 11:02   ` Steinar Bang
2009-06-18 11:42     ` Dave Goldberg
2009-06-19 11:03       ` Steinar Bang
2009-06-19 12:30         ` Vegard Vesterheim
2009-06-19 15:41           ` Steinar Bang [this message]
2009-06-18 12:27     ` David Engster
2009-06-19 11:06       ` Steinar Bang

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=m37hz8mdsq.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).