Re: auto-kill mails with "X-Spam-Flag: YES"

[Emanuel Berg <embe8573@student.uu.se>]

Lars Ingebrigtsen <larsi@gnus.org> writes:

>>> 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?

What do you mean in what buffer it is in?

Is this the code that doesn't work? (lines 2079-2086 in
gnus-score.el, Gnus v5.13)

	  ;; Evil hackery to make match usable in non-standard headers.
	  (when extra
	    (setq match (concat "[ (](" extra " \\. \"\\([^\"]*\\\\\"\\)*[^\"]*"
				(if (eq search-func 're-search-forward)
				    match
				  (regexp-quote match))
				"\\([^\"]*\\\\\"\\)*[^\"]*\")[ )]")
		  search-func 're-search-forward)) ; XXX danger?!?

What should happen, that doesn't?

What does "XXX danger" mean?

Perhaps the "evil hackery" should be removed to have
the code more palatable :)

By the way, still no one replicated this problem.
Someone other than me should try do downscore with
extra headers and

    X-Spam-Flag: YES

That way we know where to look for the problem.

-- 
underground experts united
http://user.it.uu.se/~embe8573