Gnus development mailing list
 help / color / mirror / Atom feed
From: Henrik Enberg <henrik@enberg.org>
Subject: Re: "Updating marks" spam -- how do I kill it?
Date: Mon, 27 Aug 2001 22:48:19 +0200	[thread overview]
Message-ID: <m3elpxw7os.fsf@enberg.org> (raw)
In-Reply-To: <86wv3pw88m.fsf@duchess.twilley.org> (Jack Twilley's message of "Mon, 27 Aug 2001 13:36:25 -0700")

Jack Twilley <jmt@twilley.org> writes:

>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>
> Jack> Every time I hit 'g', I get a line of "Updating marks" for each
> Jack> nnml group I have.  This is remarkably annoying and inefficient.
> Jack> Annoying because it takes time and wastes bandwidth.
>
> Simon> I changed the verbosity level to 8.
>
> Tell me how to make it go away?

(setq gnus-verbose 7)

> Jack> Inefficient because it traverses every single group instead of
> Jack> only the ones that were modified by the 'g'.
>
> Simon> The updating of marks isn't in the Gnus -> nnml direction, but
> Simon> rather the other way around.  So all groups that are checked
> Simon> for new mail have their marks updated (if necessary) as well.
>
> There has *got* to be a better way.

Is there a way to se if a specific group has new messages?
`gnus-group-get-new-news' doesn't seem to differentiate between groups.

Henrik
-- 
Could I have a drug overdose?



  parent reply	other threads:[~2001-08-27 20:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 19:09 Jack Twilley
2001-08-27 20:24 ` Kai Großjohann
2001-08-27 20:46   ` Simon Josefsson
2001-08-27 20:29 ` Simon Josefsson
2001-08-27 20:36   ` Jack Twilley
2001-08-27 20:43     ` Paul Jarc
2001-08-27 20:48     ` Henrik Enberg [this message]
2001-08-28 19:43       ` Henrik Enberg
2001-08-27 21:02     ` Simon Josefsson
2001-08-28  8:16     ` Kai Großjohann

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=m3elpxw7os.fsf@enberg.org \
    --to=henrik@enberg.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).