Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Offline mail and group cooperation
Date: Thu, 17 Oct 2002 22:15:47 +0200	[thread overview]
Message-ID: <847kggbz4c.fsf@crybaby.cs.uni-dortmund.de> (raw)
In-Reply-To: <84d6q8c03a.fsf@crybaby.cs.uni-dortmund.de>

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

> It's getting urgent for me.  I really want to be able to download all
> articles, including the read ones.

I've been looking at the patch from
http://www.gnus.org/cgi-bin/wilma_hiliter/ding/200007/msg00006.html?line=30#hilite
-- this is the one you meant?

The first hunk cannot be applied easily because the code looks very
different around that part.  (If the comment still identifies the
spot.)

I've also been thinking about changing the predicate syntax so that
the old predicates are still valid (with the same meaning), and only
new-style predicates include the unread articles.  One possibility
would be to look for each predicate whether it contains the symbols
`read' and `unread'.  If the symbols are not present, it must be an
old-style predicate, and it is rewritten: let P be the predicate,
then the rewritten predicate is (and (not read) P).

If one of the symbols `read' or `unread' are present, then the
predicate is not rewritten but just taken as-is.

But then people have to say something atrocious like (or read true)
to just fetch all articles.  This is really ugly.  Or is there a
better way to do it so that the new predicates aren't so ugly?

Simon, would you be willing to update your patch to the current
gnus-agent?  I'd test it right away.

[time passes]

I even found a good name for that variable:
gnus-agent-consider-all-articles.  It would default to nil.  And
gnus-agent-fetch-headers can just have the current behavior or include
all articles, depending on the variable.

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)



  reply	other threads:[~2002-10-17 20:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 20:11 Kai Großjohann
2002-09-23 21:19 ` Alex Schroeder
2002-09-24  8:15   ` Kai Großjohann
2002-09-24 12:41     ` Clemens Fischer
2002-09-24 14:49       ` Kai Großjohann
2002-09-24 17:17     ` Alex Schroeder
2002-09-27  2:43     ` news
2002-09-27 10:24       ` Kai Großjohann
2002-09-27 17:05         ` Christoph Garbers
2002-09-27 17:59           ` François Pinard
2002-10-02 18:40         ` Scott A Crosby
2002-09-24 11:33 ` Simon Josefsson
2002-09-24 12:11   ` Kai Großjohann
2002-09-24 12:19   ` Kai Großjohann
2002-09-25 18:34   ` Björn Torkelsson
2002-09-26  8:14     ` Kai Großjohann
2002-09-26  8:44       ` dme
2002-09-26 14:40         ` Kai Großjohann
2002-09-26 16:11         ` Wes Hardaker
2002-09-26 16:59         ` Simon Josefsson
2002-09-26 17:11           ` Kai Großjohann
2002-09-26 17:28           ` dme
2002-10-17 19:54   ` Kai Großjohann
2002-10-17 20:15     ` Kai Großjohann [this message]
2002-10-20 19:53   ` Kai Großjohann
2002-09-24 11:55 ` Reiner Steib
2002-09-24 12:16   ` Kai Großjohann
2002-09-24 12:17 ` Christoph Garbers
2002-09-27 14:14 ` Frank Schmitt
2002-09-27 14:32   ` Kai Großjohann
2002-09-27 15:36     ` Frank Schmitt
2002-10-01 19:02     ` Paul Jarc
2002-10-06 20:05 ` Kai Großjohann
2002-10-07  2:30   ` Daniel Pittman
2002-10-07 23:25   ` Clemens Fischer

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=847kggbz4c.fsf@crybaby.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).