Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Rafferty <craffert@ml.com>
Subject: Re: slow checking for new mail
Date: 08 Sep 1997 11:05:36 -0400	[thread overview]
Message-ID: <ocriuwbhmm7.fsf@ml.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "08 Sep 1997 12:48:24 +0200"

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

Lars Magne Ingebrigtsen writes:
> stephen farrell <stephen@farrell.org> writes:

>> Ok... so I wrote a bit about this before--it's really really slow for
>> me to check for new mail.  I have about 80 nnml groups, nfs mounted,
>> which are priority 1.  when i punch 1 g, it takes about 10-15 seconds
>> to incorperate new mail (even if only 1 new email).

> If you have lots of level 1 nnml groups, `1 g' will be slow.  nnml
> checks each group seperately in these cases.

My solution was to have a command that gets that just gets the new mail
once, and updates the *Group* lines of the groups that have new mail.

This works for nnml only:


[-- Attachment #2: Type: text/plain, Size: 758 bytes --]

(define-key gnus-group-mode-map [(meta control g)] 'gnus-group-get-new-nnml)

(defun gnus-group-get-new-nnml ()
  "Get new mail only."
  (interactive)
  (let ((gnus-group-new-mail-list nil)
	(nnml-prepare-save-mail-hook
	 (cons '(lambda ()
		  (setq gnus-group-new-mail-list
			(union gnus-group-new-mail-list
			       (mapcar 'car group-art))))
	       nnml-prepare-save-mail-hook)))
    (nnml-request-scan)
    (let ((gnus-group-marked (mapcar '(lambda (group)
					(concat "nnml:" group))
				     gnus-group-new-mail-list)))
      (gnus-group-get-new-news-this-group))
    (when gnus-goto-next-group-when-activating
      (gnus-group-next-unread-group 1 t))
    (gnus-summary-position-point)
    (gnus-group-list-groups)
    gnus-group-new-mail-list))


[-- Attachment #3: Type: text/plain, Size: 10 bytes --]

-- 
Colin

  reply	other threads:[~1997-09-08 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-06 12:59 stephen farrell
1997-09-07  3:46 ` Mark Eichin
1997-09-08  7:14   ` Ken Raeburn
1997-09-08 10:47     ` Lars Magne Ingebrigtsen
1997-09-08 14:07     ` David Kågedal
1997-09-08 10:48 ` Lars Magne Ingebrigtsen
1997-09-08 15:05   ` Colin Rafferty [this message]
1997-09-08 18:41     ` stephen farrell
1997-09-08 18:27   ` stephen farrell

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=ocriuwbhmm7.fsf@ml.com \
    --to=craffert@ml.com \
    /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).