mailtrainer.crm - bugfix for '--worst' mode

Existing code at step 5:

#####   Step 5 ---  Train only those worst errors
#####               Easily done, as the full filename is "coded" into
#####               the report, as well as what to train it as.

{
	match (:nextline: :pr: :type: :filename:) [:worst_retrains:] \
	 /([[:graph:]]+) +([[:graph:]]+) +([[:graph:]]+)\n/
	input [:*:filename: 0 :*:decision_length:]
	call /:do_mutilations:/
	isolate (:m_text:) /:*:_dw:/
	{
		{
			match [:type:] /G/
			output /\nConsidering :*:filename: as good\n/
			call /:test_train_good:/
...

Fix:

the line
	isolate (:m_text:) /:*:_dw:/
got to go.

Reason:
do_mutilations() will produce message content in :m_text: and
:test_train_good/spam: will pick it out of that variable. This occurs
in several spots in the script a la:

		call /:do_mutilations:/ # leaves the result in :m_text:
		call /:test_train_good:/

The isolate damaged :m_text: before training.



-- 
Met vriendelijke groeten / Best regards,

Ger Hobbelt

--------------------------------------------------
web: http://www.hobbelt.com/
 http://www.hebbut.net/
mail: [email protected]
mobile: +31-6-11 120 978
--------------------------------------------------

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/