Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: agent/imap offline reading
Date: Wed, 26 Jun 2002 10:55:15 +0200	[thread overview]
Message-ID: <iluvg86v2q4.fsf@extundo.com> (raw)
In-Reply-To: <vafwusmifx0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 26 Jun 2002 10:48:43 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> The agent currently has some hard coded default to not download
>> already read articles.  I wrote a patch long time ago (posted here)
>> that added a `read' Agent predicate to fix this, but that isn't
>> backwards compatible and means everyone has to change agent
>> predicates, which isn't good, so I'm not sure if it can be added.
>
> Can it be made backwards-compatible?  Can't you make it so that by
> default, read articles are not downloaded, like now?  Then people can
> frob their agent predicates to also download read articles.

The default value is stored in the agent predicate file, so if we
change the default the old default will still be in people's agent
predicate file.  So people with old agent predicate files that upgrade
to new gnus will start to download read articles.  The upgrade
procedure could contain a step that wraps all old predicates in a (and
read ,@OLD) but it isn't nice to do that without telling the user.
And what if the user later downgrades?  I'm not sure what Gnus does
given an unknown predicate.

But I guess it isn't impossible to fix.




  reply	other threads:[~2002-06-26  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 23:56 Danny Siu
2002-06-26  8:28 ` Simon Josefsson
2002-06-26  8:48   ` Kai Großjohann
2002-06-26  8:55     ` Simon Josefsson [this message]
2002-06-26 11:05       ` Kai Großjohann
2002-06-26 19:22   ` Danny Siu
2002-06-26 20:59     ` Simon Josefsson
2002-06-27  0:45       ` Danny Siu
2002-08-02  0:07       ` Danny Siu

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=iluvg86v2q4.fsf@extundo.com \
    --to=jas@extundo.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).