On 2009-09-10 20:18 (+0200), Adam Sjøgren wrote:
> If you set the variable I introduced, unregistering happens whenever
> spam.el changes something from spam to ham, or from ham to spam before
> it learns it again - as far as I can see (that is what happens on my
> machine anyway).
> * An email is detected as spam, but you realize that it isn't. You mark
> it as ham. spam.el unregisters it from spam and relearns it as ham.
>
> (And the other way around.)
Thanks. I wonder, though, what's the purpose of that
spam-unregister-on-reregister variable? Shouldn't it be always turned on
(non-nil)? Just to make a point: generally when the meaning of variable
starts to sounds like
(setq please-fix-this-stupid-bug t)
then why not just unconditionally fix the bug and not introduce any new
variables to confuse users?
Of course I may have missed something. No offense meant; I'm really on
the "thank you" side here. :-)
_______________________________________________
info-gnus-english mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-gnus-english
