Re: uudecoding bug?

[Vladimir Volovich <vvv@vvv.vsu.ru>]

"LMI" == Lars Magne Ingebrigtsen writes:

 LMI> Vladimir Volovich <vvv@vvv.vsu.ru> writes: What does
 LMI> (gnus-uu-reginize-string (gnus-summary-article-subject)) on one
 LMI> of these lines say?
 >>  Here is it (in russian):
 >> 
 >> "Шрифт[ ]+на[ ]+обсуждение[ ]+(TTF)[ ]+([0-9]+/7)"

 LMI> That looks ok.
 LMI> Does
 LMI> (gnus-uu-find-articles-matching)
 LMI> over one of those lines return `nil'?

Yes.

 LMI> If so, could you edebug-defun that function?

Well, i'm not so much a elisp hacker. :-) I did not find how to use
edebug-defun. I used debug-on-entry instead. Here is what happens:
gnus prepared a regexp to look for subjects, and then started to
verify matching for all subjects in the summary buffer. i.e. it
executed statements like this:

string-match("\xe48\xe60\xe58\xe64\xe62[ 	]+\xe5d\xe50[ 	]+\xe5e\xe51\xe61\xe63\xe56\xe54\xe55\xe5d\xe58\xe55[ 	]+(TTF)[ 	]+([0-9]+/7)" "Re: \xe3a\xe50\xe5f\xe58\xe62\xe55\xe5b\xe6c \xe51\xe63\xe5a\xe52\xe6b \"\xe67\".")

All of them returned nil, and no articles were found. Maybe, this is
because of multibyte/encoding/whatever?

	Best regards, -- Vladimir.