From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: gnus and imap
Date: Thu, 10 Dec 2009 15:08:51 -0500 [thread overview]
Message-ID: <87my1qiobw.fsf@uwo.ca> (raw)
In-Reply-To: <87ws0yipcv.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> I'm wondering if Vitaly or David have made any progress on the imap
> unread count. I'm using dovecot, and I regularly get wrong unread
> counts in my nnimap groups, even with
> gnus-fixup-nnimap-unread-after-getting-new-news in
> gnus-after-getting-new-news-hook.
>
> I think David's idea of adding an optional backend function which
> returns more detailed information is the way to go. The core of Gnus
> can check for this function and use it if it exists, falling back to the
> old way if not. This allows for a gradual transition without needing
> massive changes all at once.
I found another thread with promising code for the nnml backend, written
by David Hanak. It seemed like only minor details needed to be worked
out:
http://thread.gmane.org/gmane.emacs.gnus.general/56714
The thread I was referring to above discussed code written by Vitaly
Mayatskikh and included comments by a different David, David Engster:
http://thread.gmane.org/gmane.emacs.gnus.general/67238
Both seem like they were within reach of a solution to this problem that
has plagued Gnus for a long time! Maybe we can reach a consensus about
the best way to proceed, and finally get it done?
Dan
PS: There are also two solutions posted at
http://www.emacswiki.org/emacs/GnusNiftyTricks
next prev parent reply other threads:[~2009-12-10 20:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 16:14 Vitaly Mayatskikh
2008-08-19 20:12 ` Frank Schmitt
2008-08-19 22:24 ` Vitaly Mayatskikh
2008-08-20 6:42 ` Vegard Vesterheim
2008-08-20 7:41 ` Vitaly Mayatskikh
2008-08-20 16:16 ` David Engster
2008-08-21 6:26 ` Vitaly Mayatskikh
2008-08-21 11:27 ` David Engster
2008-08-21 12:57 ` Tibor Simko
2008-08-22 8:44 ` Vitaly Mayatskikh
2008-08-22 8:54 ` David Engster
2008-08-22 15:35 ` Tibor Simko
2008-08-21 15:06 ` Vitaly Mayatskikh
2008-08-21 21:15 ` Frank Schmitt
2008-08-22 12:13 ` Reiner Steib
2008-08-22 12:30 ` Vitaly Mayatskikh
2008-08-22 15:50 ` Ted Zlatanov
2008-08-22 16:10 ` Vitaly Mayatskikh
2008-08-22 16:21 ` David Engster
2008-08-22 16:27 ` Vitaly Mayatskikh
2008-08-22 17:33 ` David Engster
2008-08-22 18:11 ` Vitaly Mayatskikh
2008-08-23 9:19 ` David Engster
2008-08-23 11:32 ` Vitaly Mayatskikh
2008-08-23 14:52 ` David Engster
2008-08-24 8:47 ` Vitaly Mayatskikh
2008-08-24 18:09 ` David Engster
2008-08-24 19:29 ` Reiner Steib
2008-08-24 23:39 ` David Engster
2008-08-25 19:22 ` James Cloos
2008-08-25 0:00 ` Daniel Pittman
2008-08-25 9:46 ` David Engster
2008-08-25 18:02 ` Ted Zlatanov
2008-08-25 19:50 ` David Engster
2008-08-25 8:05 ` Vitaly Mayatskikh
2008-08-25 12:25 ` David Engster
2008-08-25 13:17 ` Vitaly Mayatskikh
2008-08-25 17:53 ` Ted Zlatanov
2008-08-24 9:18 ` Vitaly Mayatskikh
2008-08-24 10:08 ` David Engster
2008-08-26 20:40 ` Vitaly Mayatskikh
2008-09-03 11:55 ` David Engster
2008-09-21 9:57 ` David Engster
2009-12-07 18:57 ` Dan Christensen
2009-12-10 20:08 ` Dan Christensen [this message]
2009-12-11 20:36 ` David Engster
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 8:52 gnus and IMAP me
2002-07-09 9:29 ` Niklas Morberg
2002-07-09 10:17 ` me
2002-07-09 10:27 ` me
2002-07-09 10:52 ` me
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=87my1qiobw.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).