From: Maciej Matysiak <phoner@blah.pl>
Subject: Re: message sending is slooow when message-subscribed-address-functions set to gnus-find-subscribed-addresses.
Date: Thu, 06 Jun 2002 15:01:39 +0200 [thread overview]
Message-ID: <hh660wtvbg.fsf@blah.pl> (raw)
In-Reply-To: <m3n0ubrvud.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 04 Jun 2002 09:56:04 -0400")
On the 4th of June 2002 at 15:56, prj@po.cwru.edu (Paul Jarc) wrote:
> Assuming your to-list and to-address parameters don't change very
> often
they change once a month (my mail is sorted in groups which have names
like ding-l-2002-06).
> you could try this instead:
> (setq message-subscribed-regexps (gnus-find-subscribed-addresses))
thank you :) executing that code took ~15 seconds (why is it so slow?),
but now i got m-f-t with (setq message-subscribed-address-functions nil).
> Faster, but possibly less up-to-date.
i'm happy with it.
m.m.
--
use gnus, not guns!
next prev parent reply other threads:[~2002-06-06 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 3:17 Maciej Matysiak
2002-06-04 13:56 ` Paul Jarc
2002-06-06 13:01 ` Maciej Matysiak [this message]
2002-06-06 13:51 ` Paul Jarc
2002-06-06 13:54 ` 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=hh660wtvbg.fsf@blah.pl \
--to=phoner@blah.pl \
/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).