Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: gnus-agent typo?
Date: Thu, 24 Oct 2002 11:12:06 -0400	[thread overview]
Message-ID: <m3pttzvpk3.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <84u1jc9uvb.fsf@crybaby.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Thu, 24 Oct 2002 09:08:40 +0200")

kai.grossjohann@uni-duisburg.de (Kai Großjohann) wrote:
> I reverted my change and added a comment some days ago.

Ah, there it is.  I didn't see it before for some reason.  But I think
that comment would leave me with (almost) the same impression that I
got from the original code: that seen and recent articles should not
be fetched, regardless of what other marks they may have.  But that's
not what the code does.  I think this would be clearer (also
incorporating Simon's note):

--- lisp/gnus-agent.el	2002/10/23 20:32:01	6.91
+++ lisp/gnus-agent.el	2002/10/24 15:10:57
@@ -1108,9 +1108,11 @@
 	(gnus-decode-encoded-word-function 'identity)
 	(file (gnus-agent-article-name ".overview" group))
 	gnus-agent-cache)
-    ;; Add article with marks to list of article headers we want to
-    ;; fetch.  We don't want to fetch all the seen articles, and we
-    ;; don't want do fetch the recent ones, though.
+    ;; Add articles with marks to the list of article headers we want to
+    ;; fetch.  Don't fetch articles solely on the basis of a recent or seen
+    ;; mark, but do fetch recent or seen articles if they have other, more
+    ;; interesting marks.  (We have to fetch articles with boring marks
+    ;; like 'reply because otherwise the agent will remove their marks.)
     (dolist (arts (gnus-info-marks (gnus-get-info group)))
       (unless (memq (car arts) '(seen recent))
 	(setq articles (gnus-range-add articles (cdr arts)))))


paul



  parent reply	other threads:[~2002-10-24 15:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 18:05 Kai Großjohann
2002-10-21 21:23 ` Paul Jarc
2002-10-22  8:37   ` Kai Großjohann
2002-10-22 18:02     ` Paul Jarc
2002-10-23  8:07       ` Kai Großjohann
2002-10-23 15:20         ` Paul Jarc
2002-10-23 15:40           ` Kai Großjohann
2002-10-23 15:58             ` Paul Jarc
2002-10-24  7:08               ` Kai Großjohann
2002-10-24 10:26                 ` Simon Josefsson
2002-10-24 10:35                   ` Kai Großjohann
2002-10-24 15:24                     ` Simon Josefsson
2002-10-24 16:58                       ` Kai Großjohann
2002-10-24 19:20                       ` Kai Großjohann
2002-10-24 23:30                         ` Simon Josefsson
2002-10-25  8:51                           ` Kai Großjohann
2002-10-25 10:35                             ` Simon Josefsson
2002-10-25 10:48                               ` Kai Großjohann
2002-10-26 16:56                       ` Clemens Fischer
2002-10-24 15:12                 ` Paul Jarc [this message]
2002-10-24 17:03                   ` Kai Großjohann
2002-10-24 17:34                     ` Paul Jarc

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=m3pttzvpk3.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).