From: yamaoka Date: Tue, 7 Dec 2004 23:01:24 +0000 (+0000) Subject: Synch to No Gnus 200412071909. X-Git-Tag: t-gnus-6_17_4-quimby-~645 X-Git-Url: http://git.chise.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fccd1fea8691a53c72704a4d947c01abbca3ef5e;p=elisp%2Fgnus.git- Synch to No Gnus 200412071909. --- diff --git a/texi/ChangeLog b/texi/ChangeLog index 2a4a67f..eaf072f 100644 --- a/texi/ChangeLog +++ b/texi/ChangeLog @@ -1,3 +1,11 @@ +2004-12-07 Teodor Zlatanov + + * gnus.texi (Filtering Spam Using The Spam ELisp Package) + (Spam ELisp Package Filtering of Incoming Mail) + (Spam ELisp Package Sorting and Score Display in Summary Buffer): + replace @code{spam.el} with @file{spam.el} where the file spam.el + is intended as the subject + 2004-12-06 Reiner Steib * gnus-news.texi: Mention `gnus-summary-limit-to-recipient' and diff --git a/texi/gnus-ja.texi b/texi/gnus-ja.texi index 2e01fb2..1b64671 100644 --- a/texi/gnus-ja.texi +++ b/texi/gnus-ja.texi @@ -21725,7 +21725,7 @@ Gnus $B$O(B hashcash $B%/%C%-!<$rG'>Z$9$k$3$H$,$G$-$^$9$,!"H$7$F2<$5$$!#(B @cindex spam-initialize -@code{spam.el} $B$r;H$&$K$O!"(B@code{spam.el} $B$r<+F0FI$_9~$_(B (autoload) $B$7(B +@code{spam.el} $B$r;H$&$K$O!"(B@file{spam.el} $B$r<+F0FI$_9~$_(B (autoload) $B$7(B $B$F(B @code{spam.el} $B$N3F%U%C%/$r%$%s%9%H!<%k$9$k$?$a$K!"4X(B $B?t(B @code{spam-initialize} $B$r(B @strong{$B $B8!::$HF1;~$KL@$i$+$K(B @code{spam-split} $B$rr7o(B $BIU$-$NFI$_9~$_$,9T$o$l$k$+$i$G$9!#(B @@ -22196,7 +22196,7 @@ Ham $B$,(B spam $B%0%k!<%W$+$i0\F0$5$l$kA0$K0u$r>C$7$?$$>l9g$O!"$3$NJQ?t$r%;% @code{X-Spam-Status} $B%X%C%@!<$,;H$o$l$^$9!#(B@code{spam-use-bogofilter} $B$r(B $B;H$&>l9g$O!"(B@code{X-Bogosity} $B$,;H$o$l$^$9!#(B@code{spam-use-crm114} $B$r;H(B $B$&$N$J$i$P!"(BCRM114 $B%9%3%"!&%U%)!<%^%C%H$K9gCW$9$k!"$$$:$l$+$N%X%C%@$,;H(B -$B$o$l$^$9!#(B@code{spam.el} $B$r%m!<%I$9$k(B @emph{$BA0(B} $B$K!"E,@Z$J%P%C%/%(%s%IJQ(B +$B$o$l$^$9!#(B@file{spam.el} $B$r%m!<%I$9$k(B @emph{$BA0(B} $B$K!"E,@Z$J%P%C%/%(%s%IJQ(B $B?t$r(B t $B$K@_Dj$9$k8B$j!"$&$^$/$$$/$G$7$g$&!#(B@code{spam.el} $B$O!"(BGnus $B$,Fb(B $BItE*$KI,MW$H$9$k%X%C%@!<$N%j%9%H$K!"@5$7$$%X%C%@!<$r<+F0E*$KDI2C$7$^$9!#(B diff --git a/texi/gnus.texi b/texi/gnus.texi index f384185..96eea00 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -22634,7 +22634,7 @@ events. See @xref{Spam ELisp Package Sequence of Events}. @cindex spam-initialize To use @code{spam.el}, you @strong{must} run the function -@code{spam-initialize} to autoload @code{spam.el} and to install the +@code{spam-initialize} to autoload @file{spam.el} and to install the @code{spam.el} hooks. There is one exception: if you use the @code{spam-use-stat} (@pxref{spam-stat spam filtering}) setting, you should turn it on before @code{spam-initialize}: @@ -22644,7 +22644,7 @@ should turn it on before @code{spam-initialize}: (spam-initialize) @end example -So, what happens when you load @code{spam.el}? +So, what happens when you load @file{spam.el}? First, some hooks will get installed by @code{spam-initialize}. There are some hooks for @code{spam-stat} so it can save its databases, and @@ -22683,7 +22683,7 @@ You must have Bogofilter installed for that command to work properly. @end table -Also, when you load @code{spam.el}, you will be able to customize its +Also, when you load @file{spam.el}, you will be able to customize its variables. Try @code{customize-group} on the @samp{spam} variable group. @@ -22894,7 +22894,7 @@ spam checks for your nnmail split vs. your nnimap split. Go crazy. You should still have specific checks such as @code{spam-use-regex-headers} set to @code{t}, even if you specifically invoke @code{spam-split} with the check. The reason is -that when loading @code{spam.el}, some conditional loading is done +that when loading @file{spam.el}, some conditional loading is done depending on what @code{spam-use-xyz} variables you have set. This is usually not critical, though. @@ -23103,7 +23103,7 @@ back end, the @code{X-Spam-Status} header will be used. If you use @code{spam-use-bogofilter}, the @code{X-Bogosity} header will be used. If you use @code{spam-use-crm114}, any header that matches the CRM114 score format will be used. As long as you set the appropriate back end -variable to t @emph{before} you load @code{spam.el}, you will be +variable to t @emph{before} you load @file{spam.el}, you will be fine. @code{spam.el} will automatically add the right header to the internal Gnus list of required headers.