From: Ted Zlatanov <tzz@lifelogs.com>
Subject: spam.el spam-summary-prepare-exit rewrite (was: ham destination bugs)
Date: Thu, 08 Jun 2006 16:54:06 -0400 [thread overview]
Message-ID: <g69ejxz5pxt.fsf_-_@CN1374059D0130.kendall.corp.akamai.com> (raw)
In-Reply-To: <v964nakssy.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 20 Feb 2006 15:29:01 +0100")
On 20 Feb 2006, reinersteib+gmane@imap.cc wrote:
...
> Copying to nnml+personal:misc.Spam.2006: (672 674 676 677 679)...
> Group misc.Fi selected
> Couldn't Copy article 672: Group misc.Fi selected
...
> "misc.Fi" is a completely unrelated group on "nnml+personal" (possibly
> it's the most recently created group on "nnml+personal"). I'm
> puzzled.
I think this is related to a bug I noticed and brought up a while
ago. Basically when spam.el does group-exit processing, Gnus will
refresh *every* group in some range I can't figure out, usually at
least 1 group. It's as if Gnus went and pressed M-g automatically on
a bunch of groups for no apparent reason.
I've thought about the current group-exit processing, with all the
registration/unregistration stuff, and I think I'll redo the whole
spam-summary-prepare-exit function and what depends on it. As you
know I redid the backends a while ago; I should be able to take
advantage of that and produce cleaner code with fewer bugs.
If anyone is interested in helping or suggesting changes, now is the
time to speak up.
Ted
next prev parent reply other threads:[~2006-06-08 20:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 20:59 Gnus manual update Chong Yidong
2006-02-06 19:18 ` Ted Zlatanov
2006-02-06 20:19 ` Chong Yidong
2006-02-06 20:31 ` spam manual update for Gnus (was: Gnus manual update) Ted Zlatanov
2006-02-06 22:49 ` spam manual update for Gnus Reiner Steib
2006-02-08 20:20 ` Ted Zlatanov
2006-02-08 20:56 ` Chong Yidong
2006-02-09 15:00 ` spam.el: Bugs, compatibility with v5-10 (was: spam manual update for Gnus) Reiner Steib
2006-02-13 19:04 ` spam.el: Bugs, compatibility with v5-10 Ted Zlatanov
2006-02-13 22:36 ` Emacs 20.7 compatibility in v5-10 (was: spam.el: Bugs, compatibility with v5-10) Reiner Steib
2006-03-20 19:51 ` Emacs 20.7 compatibility in v5-10 Ted Zlatanov
2006-03-20 20:38 ` Reiner Steib
2006-02-13 19:15 ` ham destination bugs (was: spam.el: Bugs, compatibility with v5-10) Ted Zlatanov
2006-02-14 15:04 ` ham destination bugs Reiner Steib
2006-02-20 14:29 ` Reiner Steib
2006-05-27 10:17 ` Reiner Steib
2006-05-30 13:55 ` Ted Zlatanov
2006-06-08 20:54 ` Ted Zlatanov [this message]
2006-04-19 14:23 ` spam manual update for Gnus Reiner Steib
2006-04-20 18:18 ` Ted Zlatanov
2006-04-20 18:38 ` Chong Yidong
2006-04-20 20:08 ` Reiner Steib
2006-04-20 23:20 ` Miles Bader
2006-04-20 18:45 ` Ted Zlatanov
2006-02-06 20:25 ` message mode screwy (was: Gnus manual update) Ted Zlatanov
2006-02-08 16:52 ` message mode screwy Reiner Steib
2006-02-09 15:37 ` Ted Zlatanov
2006-02-13 18:58 ` Ted Zlatanov
2006-02-13 22:15 ` Adam Sjøgren
2006-02-13 22:39 ` Reiner Steib
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=g69ejxz5pxt.fsf_-_@CN1374059D0130.kendall.corp.akamai.com \
--to=tzz@lifelogs.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).