From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: Fetching all messages into the Agent
Date: Thu, 14 Jun 2012 07:57:40 +0000 [thread overview]
Message-ID: <xafsjdymikr.fsf@this.is.really.invalid> (raw)
In-Reply-To: <xgsjdzfgzs.fsf@news.eternal-september.org>
Richard Riley <rileyrg@gmail.com> writes:
> When firing off J s in the group buffer is there a way, or could there
> please, to give some sort of progress feedback? As it is gnus just "locks
> up" (ie fetches with no indication its doing anything) , sometimes for a
> long time, with no indication its doing anything! Possibly just message
> the group currently being fetched.
When I used the agent, I used the following. I hereby place it in the
public domain (although I doubt it passes the 'originality' test :) )
diff --git a/lisp/gnus-agent.el b/lisp/gnus-agent.el
index 3597037..530ebd6 100644
--- a/lisp/gnus-agent.el
+++ b/lisp/gnus-agent.el
@@ -1570,10 +1570,12 @@ downloaded into the agent."
(date (time-to-days (current-time)))
(case-fold-search t)
pos crosses id
- (file-name-coding-system nnmail-pathname-coding-system))
+ (file-name-coding-system nnmail-pathname-coding-system)
+ (n 1) total)
(setcar selected-sets (nreverse (car selected-sets)))
(setq selected-sets (nreverse selected-sets))
+ (setq total (reduce '+ (mapcar 'length selected-sets)))
(gnus-make-directory dir)
(gnus-message 7 "Fetching articles for %s..."
@@ -1587,9 +1589,10 @@ downloaded into the agent."
(with-temp-buffer
(let (article)
(while (setq article (pop articles))
- (gnus-message 10 "Fetching article %s for %s..."
- article
+ (gnus-message 7 "Fetching article %d of %d for %s..."
+ n total
(gnus-agent-decoded-group-name group))
+ (incf n)
(when (or
(gnus-backlog-request-article group article
nntp-server-buffer)
next prev parent reply other threads:[~2012-06-14 7:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 14:01 Richard Riley
2012-06-14 7:57 ` Robert Pluim [this message]
2012-06-14 7:58 ` Eric S Fraga
2012-06-14 10:17 ` Tassilo Horn
2012-06-14 14:17 ` Wolfgang Jenkner
2012-06-14 15:45 ` Eric S Fraga
2012-06-14 17:41 ` Wolfgang Jenkner
2012-06-14 16:04 ` Tassilo Horn
2012-06-15 15:27 ` Eric S Fraga
2012-06-15 15:40 ` Eric S Fraga
2012-06-20 18:33 ` Lars Magne Ingebrigtsen
2012-06-21 8:37 ` Eric S Fraga
2012-06-21 11:33 ` Richard Riley
2012-06-21 15:35 ` Vagn Johansen
2012-12-23 2:18 ` Ted Zlatanov
2012-12-24 20:30 ` Lars Ingebrigtsen
2012-12-24 20:34 ` Lars Ingebrigtsen
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=xafsjdymikr.fsf@this.is.really.invalid \
--to=rpluim@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).