Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Rafferty <craffert@spspme.ml.com>
Subject: Re: miscellaneous Gnus questions
Date: 24 Jun 1996 09:46:17 -0400	[thread overview]
Message-ID: <ocrlohd1fiu.fsf@spssunp.spspme.ml.com> (raw)
In-Reply-To: Joe Wells's message of 22 Jun 1996 16:08:40 -0400

"Joe" == Joe Wells <jbw@cs.bu.edu> writes:
"Lars" == You Know Who <ynw@you.know.where> writes:

Lars> There is no command to re-scan a particular server.
Lars> `(gnus-request-scan SERVER)' will do that for you.  Perhaps there
Lars> should be a command as well?

Joe> I think there should be a keybinding for this.  Checking for new mail is
Joe> quick, while checking for new news is slow.  Since the "g" command
Joe> combines these two, this unnecessarily slows down checking for new mail.

The only problem with calling `gnus-request-scan' directly is that it
does not update the *Group* buffer.  I use nnml.  Below is my solution.
If someone wants to make this a little more general (mh, etc.), be my
guest.  I have already sent in my papers.

(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))

-- 
Colin


  reply	other threads:[~1996-06-24 13:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-18 23:30 Joe Wells
1996-06-19  6:21 ` Lars Magne Ingebrigtsen
1996-06-19 12:46   ` Jack Vinson
1996-06-19 13:12     ` Lars Magne Ingebrigtsen
1996-06-22 20:08   ` Joe Wells
1996-06-24 13:46     ` Colin Rafferty [this message]
1996-08-28  6:22     ` Lars Magne Ingebrigtsen
1996-08-28 22:26       ` Roger Williams
1996-08-29  0:54         ` Roger Williams
1996-06-25 21:48   ` Hallvard B Furuseth
1996-06-19  8:26 ` Per Abrahamsen

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=ocrlohd1fiu.fsf@spssunp.spspme.ml.com \
    --to=craffert@spspme.ml.com \
    --cc=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).