From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: ding@gnus.org
Subject: Re: gnus and imap
Date: Thu, 21 Aug 2008 08:26:12 +0200 [thread overview]
Message-ID: <m3wsiahojf.fsf@gravicappa.englab.brq.redhat.com> (raw)
In-Reply-To: <877iabwtjx.fsf@randomsample.de> (David Engster's message of "Wed, 20 Aug 2008 18:16:34 +0200")
David Engster <deng@randomsample.de> writes:
> However, saying that adding this feature to all back ends is "no
> problem" seems a bit optimistic to me.
All, what it needs, is to fill gnus-info-unread (possibly, with the same
value as in active info). Overall changes in backends are quite small,
see: http://repo.or.cz/w/more-gnus.git?a=commitdiff;h=5345887a980cdd001a7c48e68143106cbd94efae
> Gnus has lots of back ends (close
> to 30), and there are external back ends like nnshimbun which are not
> part of Gnus. So in my opinion the old code should be kept and used as a
> fall-back method for back ends which do not store the unread sequence in
> the info list.
Ok, sounds reasonable. I'll try to fix Gnus for using gnus-info-unread
when possible. If backend wants to deliver articles in sequence set, it
should fill gnus-info-unread, otherwise Gnus will take bits from
gnus-active.
As I found, a lot of old code in Gnus simply doesn't work (nnir + imap,
agent + imap). Is it a good idea to keep infrastructure for this broken
code at all?
--
wbr, Vitaly
next prev parent reply other threads:[~2008-08-21 6:26 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 [this message]
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
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=m3wsiahojf.fsf@gravicappa.englab.brq.redhat.com \
--to=v.mayatskih@gmail.com \
--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).