From: Mike McEwan <mike@lotusland.demon.co.uk>
Subject: [patch] `undownloaded' marks not displayed for `old' headers
Date: 13 Jul 1998 20:04:23 +0100 [thread overview]
Message-ID: <m3vhp1o9mw.fsf@lotusland.demon.co.uk> (raw)
A little annoyance I noticed. When selecting a group covered by the
Agent and limiting the number of articles to something less than that
available, the `gnus-undownloaded-mark' ?\@ is not displayed for `old'
headers fetched because of `gnus-fetch-old-headers' being `t'.
The patch below fixes this for me:
--- ChangeLog.orig Sat Jul 11 02:05:48 1998
+++ ChangeLog Mon Jul 13 19:39:48 1998
@@ -1,3 +1,8 @@
+1998-07-13 Mike McEwan <mike@lotusland.demon.co.uk>
+
+ * gnus-sum.el (gnus-select-newsgroup): Don't call the Agent to
+ mark articles as read until *all* headers have been retrieved.
+
Sat Jul 11 03:03:53 1998 Lars Magne Ingebrigtsen <larsi@menja.ifi.uio.no>
* gnus.el: Gnus v5.6.24 is released.
--- gnus-sum.el.orig Sat Jul 11 02:05:50 1998
+++ gnus-sum.el Mon Jul 13 19:22:38 1998
@@ -3915,15 +3915,15 @@
;; Removed marked articles that do not exist.
(gnus-update-missing-marks
(gnus-sorted-complement fetched-articles articles))
- ;; Let the Gnus agent mark articles as read.
- (when gnus-agent
- (gnus-agent-get-undownloaded-list))
;; We might want to build some more threads first.
(when (and gnus-fetch-old-headers
(eq gnus-headers-retrieved-by 'nov))
(if (eq gnus-fetch-old-headers 'invisible)
(gnus-build-all-threads)
(gnus-build-old-threads)))
+ ;; Let the Gnus agent mark articles as read.
+ (when gnus-agent
+ (gnus-agent-get-undownloaded-list))
;; Check whether auto-expire is to be done in this group.
(setq gnus-newsgroup-auto-expire
(gnus-group-auto-expirable-p group))
--
Mike.
reply other threads:[~1998-07-13 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3vhp1o9mw.fsf@lotusland.demon.co.uk \
--to=mike@lotusland.demon.co.uk \
/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).