From: Lars Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: auto-kill mails with "X-Spam-Flag: YES"
Date: Sat, 20 Feb 2016 19:34:30 +1100 [thread overview]
Message-ID: <87k2lzn5k9.fsf@gnus.org> (raw)
In-Reply-To: <mailman.4888.1455669521.843.info-gnus-english@gnu.org> (Emanuel Berg's message of "Wed, 17 Feb 2016 01:38:17 +0100")
Emanuel Berg <embe8573@student.uu.se> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>>> But in Gnus v5.13, when the debugger is at line
>>> 2085 in gnus-score.el, in `gnus-score-string',
>>> *Headers* contains: ((To .
>>> "<embe8573@student.uu.se>") (X-Spam-Flag . "YES")
>>> (Subject . "=?utf-8?B?TWluIGZpdHRhIHbDpXQ=?="))
>>> After that *Headers* doesn't change until the
>>> function is done.
>>
>> Geez, the call sequence there is hard to follow...
>> hm... Well, while debugging, I think the
>> edebug-outside-buffer variable should tell you what
>> buffer all this is taking place in?
>
> `edebug-outside-buffer' is
>
> #<buffer *Headers*>
Hm. Then that can't be the correct buffer. Does anybody know of a way
to make edebug tell you what buffer it's currently in?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-20 8:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3558.1454557630.843.info-gnus-english@gnu.org>
2016-02-07 3:50 ` Lars Ingebrigtsen
2016-02-07 4:39 ` Emanuel Berg
[not found] ` <mailman.3850.1454819959.843.info-gnus-english@gnu.org>
2016-02-07 4:44 ` Lars Ingebrigtsen
2016-02-07 5:01 ` Emanuel Berg
[not found] ` <mailman.3852.1454821323.843.info-gnus-english@gnu.org>
2016-02-07 5:23 ` Lars Ingebrigtsen
2016-02-08 0:48 ` Emanuel Berg
[not found] ` <mailman.3977.1454892539.843.info-gnus-english@gnu.org>
2016-02-08 4:48 ` Lars Ingebrigtsen
2016-02-08 22:52 ` Emanuel Berg
[not found] ` <mailman.4132.1454971965.843.info-gnus-english@gnu.org>
2016-02-08 23:39 ` Lars Ingebrigtsen
2016-02-09 2:26 ` Emanuel Berg
[not found] ` <mailman.4158.1454984781.843.info-gnus-english@gnu.org>
2016-02-09 23:47 ` Lars Ingebrigtsen
2016-02-10 0:50 ` Emanuel Berg
[not found] ` <mailman.4270.1455065439.843.info-gnus-english@gnu.org>
2016-02-10 3:04 ` Lars Ingebrigtsen
2016-02-11 0:50 ` Emanuel Berg
[not found] ` <mailman.4358.1455151881.843.info-gnus-english@gnu.org>
2016-02-11 4:01 ` Lars Ingebrigtsen
2016-02-17 0:38 ` Emanuel Berg
[not found] ` <mailman.4888.1455669521.843.info-gnus-english@gnu.org>
2016-02-20 8:34 ` Lars Ingebrigtsen [this message]
2016-02-21 0:44 ` Emanuel Berg
[not found] ` <mailman.5253.1456015518.843.info-gnus-english@gnu.org>
2016-02-21 2:43 ` Lars Ingebrigtsen
2016-02-21 3:29 ` Emanuel Berg
2016-02-08 1:27 ` Emanuel Berg
2016-02-04 3:46 Emanuel Berg
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=87k2lzn5k9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@gnu.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).