From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: The new registry errors when spam.el is moving messages
Date: Thu, 21 Apr 2011 15:26:43 -0500 [thread overview]
Message-ID: <878vv3qrjw.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mvcy8lb9q.fsf@jpl.org>
On Thu, 21 Apr 2011 09:05:05 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
KY> Ted Zlatanov <tzz@lifelogs.com> wrote:
>> You mean the mail-header or the CL changes?
KY> I meant `mail-header', that never works unless the variable named
KY> `headers' is bound. Try: (mail-header "Cc" nil)
KY> So I replaced it with things similar to the original. And I noticed,
KY> it never works, either. In `gnus-registry-action':
...
I fixed this: we need to use the extra header slot (`mail-header-extra')
and that's an alist of headers. But the user needs to add To and Cc to
`gnus-extra-headers', so I explained that in the package commentary.
I actually think To and Cc should be in `gnus-extra-headers' by default.
Is there any reason not to add them? The extra memory usage is
negligible.
>> It was working fine for me before the changes.
KY> Because some mis-designed functions are hidden by `ignore-errors',
KY> I thought.
Yes. Oh, but it was nicely quiet, wasn't it? ;)
>> Other than the bug Andre Cohen reported with followed-groups,
KY> Although I've never used it, I can imagine it doesn't work for To
KY> and Cc headers. That's why I feel it incomplete. To achieve it,
KY> maybe other Gnus resources need to be changed.
Fortunately I think we're OK now.
Thanks for working on this.
Ted
next prev parent reply other threads:[~2011-04-21 20:26 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 [this message]
2011-04-21 23:09 ` Katsumi Yamaoka
2011-04-21 23:26 ` Ted Zlatanov
2011-04-20 20:55 ` Ted Zlatanov
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=878vv3qrjw.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).