From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: The new registry errors when spam.el is moving messages
Date: Wed, 20 Apr 2011 15:55:31 -0500 [thread overview]
Message-ID: <87zknkd4n0.fsf@lifelogs.com> (raw)
In-Reply-To: <8739ld198t.fsf@member.fsf.org>
On Wed, 20 Apr 2011 12:56:50 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote:
TH> it seems the problem is not the movement made my spam.el but the
TH> deletion of the message (which movement implies). When I delete some
TH> message using B DEL and quit the summary, I get a similar error.
TH> Debugger entered--Lisp error: (wrong-type-argument listp [8381 "Einladung zum iCal-Ereignis: BA Becker" "\"Dr. Volker Riediger\" <riediger@uni-koblenz.de>" #("Wed, 13 Apr 2011 15:05:56 +0200" 0 1 (gnus-time (19877 40884))) "<A1C65A0F-D87A-43F1-A0D0-0E06BAFA17EE@uni-koblenz.de>" nil 8181 3 nil ((To . "Horn Tassilo <horn@uni-koblenz.de>"))])
TH> gnus-registry-action(delete [8381 "Einladung zum iCal-Ereignis: BA Becker" "\"Dr. Volker Riediger\" <riediger@uni-koblenz.de>" #("Wed, 13 Apr 2011 15:05:56 +0200" 0 1 (gnus-time (19877 40884))) "<A1C65A0F-D87A-43F1-A0D0-0E06BAFA17EE@uni-koblenz.de>" nil 8181 3 nil ((To . "Horn Tassilo <horn@uni-koblenz.de>"))] "nnimap+Uni:INBOX" nil nil)
TH> run-hook-with-args(gnus-registry-action delete [8381 "Einladung zum iCal-Ereignis: BA Becker" "\"Dr. Volker Riediger\" <riediger@uni-koblenz.de>" #("Wed, 13 Apr 2011 15:05:56 +0200" 0 1 (gnus-time (19877 40884))) "<A1C65A0F-D87A-43F1-A0D0-0E06BAFA17EE@uni-koblenz.de>" nil 8181 3 nil ((To . "Horn Tassilo <horn@uni-koblenz.de>"))] "nnimap+Uni:INBOX" nil nil)
TH> gnus-summary-delete-article(nil)
TH> call-interactively(gnus-summary-delete-article nil nil)
Gnus is calling `gnus-registry-action' with a good data header, but the
change Yamaoka-san made to remove the dependency on mailheader.el in
2c311f43f25dbb0a0353712573d06496bd93ace2 seem to have broken it. I'll
wait for him to decide how to resolve this.
I also used `ignore-errors' around this call, which may have been hiding
the error anyhow, but that's because in many cases the header is not
included by default. I don't know much about the data header so if
anyone has better suggestions, let me and Yamaoka-san know.
Thanks
Ted
prev parent reply other threads:[~2011-04-20 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 10:04 Tassilo Horn
2011-04-20 10:56 ` Tassilo Horn
2011-04-20 13:01 ` Katsumi Yamaoka
2011-04-20 18:34 ` Ted Zlatanov
2011-04-21 0:05 ` Katsumi Yamaoka
2011-04-21 20:26 ` Ted Zlatanov
2011-04-21 23:09 ` Katsumi Yamaoka
2011-04-21 23:26 ` Ted Zlatanov
2011-04-20 20:55 ` Ted Zlatanov [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=87zknkd4n0.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).