Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: gnus processing getting out of hand (timewise)
Date: Fri, 31 Aug 2001 00:21:08 +0200	[thread overview]
Message-ID: <vaf66b5w5nv.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m1bskyga5m.fsf@reader.newsguy.com> (Harry Putnam's message of "Wed, 29 Aug 2001 08:26:13 -0700")

Harry Putnam <reader@newsguy.com> writes:

> I'm not sure what things in there may be the big hogs, but suspect
> people here would know at a glance.

Hm.  I can't see much.  The summary line format might be a problem for
entering a group.  With (setq gnus-verbose 10) you should see when
Gnus starts to generate the summary buffer -- if that takes too long
you might twiddle the summary line format.

Does it help to add (gnus-compile) just before (gnus-agentize)?

kai
-- 
Symbol's function definition is void: signature


      reply	other threads:[~2001-08-30 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29 15:26 Harry Putnam
2001-08-30 22:21 ` Kai Großjohann [this message]

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=vaf66b5w5nv.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).