\e$B5-;v?t!#\e(B
@item S
\e$BI=Bj$NJ8;zNs!#\e(B@code{gnus-list-identifiers} \e$B$N@_Dj$K$h$C$F%a!<%j%s%0%j%9%H\e(B
-\e$B$NI8<1$,:o=|$5$l$^$9!#\e(B(@xref{Article Hiding})\e$B!#\e(B
+\e$B$NI8<1$,:o=|$5$l$^$9!#\e(B@xref{Article Hiding}\e$B!#\e(B
@item s
\e$B%9%l%C%I\e(B (thread) \e$B$N4p5-;v$G$"$k$H$-$+D>A0$N5-;v$,0c$&I=Bj$N$H$-$O$=$NBj\e(B
\e$BL>$G!"$=$l0J30$O\e(B @code{gnus-summary-same-subject}\e$B!#\e(B
(\e$B$b$7$"$J$?$,!"\e(B@code{\e$B%k!<%H\e(B} (root) \e$B$G$"$j!"\e(B@code{\e$B%]%9%H%^%9%?!<\e(B}
(postmaster) \e$B$G$b$"$j!"\e(B@code{\e$B%k!<%H\e(B} \e$B$K\e(B @code{\e$B%]%9%H%^%9%?!<\e(B} \e$B$X$N%a!<%k\e(B
\e$B$r<u$1<h$C$?>l9g$O!"$=$l$r\e(B @code{\e$B%]%9%H%^%9%?!<\e(B} \e$B$K$b:FAw$7$?$$$H;W$&$G\e(B
-\e$B$7$g$&!#\e(BOrdnung mu\e,A_\e(B sein!)
+\e$B$7$g$&!#\e(BOrdnung mu\e.A\eN_ sein!)
\e$B$3$NL?Na$O%W%m%;%9\e(B/\e$B@\F,0z?t$N=,47$K=>$$$^$9\e(B (@pxref{Process/Prefix})\e$B!#\e(B
@item gnus-sort-gathered-threads-function
@vindex gnus-sort-gathered-threads-function
-@c TRANSLATEME
-Sometimes, particularly with mailing lists, the order in which mails
-arrive locally is not necessarily the same as the order in which they
-arrived on the mailing list. Consequently, when sorting sub-threads
-using the default @code{gnus-thread-sort-by-number}, responses can end
-up appearing before the article to which they are responding to. Setting
-this variable to an alternate value
-(e.g. @code{gnus-thread-sort-by-date}), in a group's parameters or in an
-appropriate hook (e.g. @code{gnus-summary-generate-hook}) can produce a
-more logical sub-thread ordering in such instances.
+\e$B$H$-$I$-!"FC$K%a!<%j%s%0%j%9%H$G!"<j85$K%a!<%k$,E~Ce$9$k=gHV$OI,$:$7%a!<\e(B
+\e$B%j%s%0%j%9%H$KE~Ce$7$?=gHV$HF1$8$G$OL5$$$3$H$,$"$j$^$9!#=>$C$F!"I{%9%l%C\e(B
+\e$B%I$r=i4|@_Dj$N\e(B @code{gnus-thread-sort-by-number} \e$B$GJB$S49$($k$H!"1~Ez$N\e(B
+\e$BJ}$,$=$l$,1~Ez$7$F$$$k5-;v$h$j@h$K8=$l$k$3$H$,$"$j$^$9!#%0%k!<%W%Q%i%a!<\e(B
+\e$B%?$dE,@Z$J%U%C%/\e(B (\e$BNc$($P\e(B @code{gnus-summary-generate-hook}) \e$B$G$3$NJQ?t$r\e(B
+\e$BBe$o$j$NCM\e(B (\e$BNc$($P!"\e(B@code{gnus-thread-sort-by-date}) \e$B$K@_Dj$9$k$3$H$G!"\e(B
+\e$B$=$N$h$&$J>l9g$K!"$h$jO@M}E*$JI{%9%l%C%I$N=gHV$r@8@.$9$k$3$H$,$G$-$^$9!#\e(B
@end table
@kindex W W l (Summary)
@findex gnus-article-hide-list-identifiers
@vindex gnus-list-identifiers
-@c TRANSLATEME
-Hide list identifiers specified in @code{gnus-list-identifiers}. Theese
-are strings some list servers add to the beginning of all @code{Subject}
-headers---for example, @samp{[zebra 4711]}.
+@code{gnus-list-identifiers} \e$B$G;XDj$5$l$F$$$k%a!<%j%s%0%j%9%H$NI8<1$r1#\e(B
+\e$B$7$^$9!#$3$l$i$O$$$/$D$+$N%j%9%H$N%5!<%P!<$,A4$F$N\e(B @code{Subject} \e$B%X%C%@!<\e(B
+\e$B$N:G=i$K$D$1$kJ8;zNs$G$9\e(B---\e$BNc$($P!"\e(B@samp{[zebra 4711]}\e$B!#\e(B
@table @code
@item gnus-list-identifiers
@vindex gnus-list-identifiers
-@c TRANSLATEME
-A regular expression that matches list identifiers to be removed from
-subject. This can also be a list of regular expressions.
+\e$BI=Bj$+$i:o=|$5$l$k$Y$-I8<1$N%j%9%H$K9gCW$9$k@55,I=8=$G$9!#$3$l$O@55,I=8=\e(B
+\e$B$N%j%9%H$G$"$k$3$H$b$G$-$^$9!#\e(B
@end table
\e$B@_Dj$7$^$9!#0J2<$O@_Dj$G$-$kJQ?t$N0lMw$G$9$,!"$^$:$3$l$i$NJQ?t$N<h$jF@$k\e(B
\e$BCM$r5DO@$7$^$9!#\e(B
-@c TRANSLATEME
-Note: Some values, while valid, make little sense. Check the list below
-for sensible values.
+\e$BCm0U\e(B: \e$B$$$/$D$+$NCM$O!"M-8z$JCM$G$9$,!"$[$H$s$I0UL#$rL5$7$^$;$s!#0UL#$N$"\e(B
+\e$B$kCM$O2<$N0lMw$rD4$Y$F$/$@$5$$!#\e(B
@enumerate
@item
(typep "text/x-vcard"))
@end lisp
-@item
-@code{mime}: @code{gnus-show-mime} \e$B$NCM$,\e(B nil \e$B$G$J$1$l$P$3$N07$$$r<B9T$7\e(B
-\e$B$^$9!#\e(B
-
@end enumerate
@c FIXTGNUS Is this true?
\e$B0J2<$N07$$$N%*%W%7%g%s$,;HMQ2DG=$G$9!#$3$l$r%+%9%?%^%$%:$9$k$?$a$N:G$b4J\e(B
\e$BC1$JJ}K!$O\e(B @code{gnus-article-treat} \e$B%+%9%?%^%$%:%0%k!<%W$rD4::$9$k$3$H\e(B
-\e$B$G$9!#\e(B
-@c TRANSLATEME
-Values in brackets are suggested sensible values. Others are possible
-but those listed are probably sufficient for most people.
-
+\e$B$G$9!#4]3g8L$NCf$NCM$ODs0F$5$l$F$$$k0UL#$N$"$kCM$G$9!#B>$N$b$N$b2DG=$G$9\e(B
+\e$B$,!"$[$H$s$I$N?M$O$*$=$i$/$3$3$K0lMwI=<($5$l$F$$$k$b$N$G==J,$G$7$g$&!#\e(B
@table @code
@item gnus-treat-highlight-signature (t, last)
* Mail Sources:: Gnus \e$B$K$I$3$+$i%a!<%k$r<h$C$F$/$k$+$rCN$i$;$k!#\e(B
* Mail Backend Variables:: \e$B%a!<%k$N07$$$r%+%9%?%^%$%:$9$k$?$a$NJQ?t!#\e(B
* Fancy Mail Splitting:: Gnus \e$B$OF~$C$FMh$?%a!<%k$NLS$N$h$&$JJ,N%$r$9$k$3$H$,$G$-$k!#\e(B
-@c TRANSLATEME
-* Group Mail Splitting:: Use group customize to drive mail splitting.
+* Group Mail Splitting:: \e$B%a!<%kJ,3d$r6nF0$9$k$?$a$K%0%k!<%W\e(B
+ \e$B%+%9%?%^%$%:$r;H$&!#\e(B
* Incorporating Old Mail:: \e$B$"$J$?$,;}$C$F$$$k8E$$%a!<%k$r$I$&$9$k$+\e(B?
* Expiring Mail:: \e$BM_$7$/$J$$%a!<%k$r<h$j=|$/!#\e(B
* Washing Mail:: \e$B<hF@$7$?%a!<%k$+$i7y$J$b$N$r<h$j=|$/!#\e(B
@node Group Mail Splitting
-@c TRANSLATEME
-@subsection Group Mail Splitting
+@subsection \e$B%0%k!<%W%a!<%kJ,3d\e(B
@cindex mail splitting
@cindex group mail splitting
@findex gnus-group-split
-@c TRANSLATEME
-If you subscribe to dozens of mailing lists but you don't want to
-maintain mail splitting rules manually, group mail splitting is for you.
-You just have to set @var{to-list} and/or @var{to-address} in group
-parameters or group customization and set @code{nnmail-split-methods} to
-@code{gnus-group-split}. This splitting function will scan all groups
-for those parameters and split mail accordingly, i.e., messages posted
-from or to the addresses specified in the parameters @var{to-list} or
-@var{to-address} of a mail group will be stored in that group.
-
-Sometimes, mailing lists have multiple addresses, and you may want mail
-splitting to recognize them all: just set the @var{extra-aliases} group
-parameter to the list of additional addresses and it's done. If you'd
-rather use a regular expression, set @var{split-regexp}.
-
-All these parameters in a group will be used to create an
-@code{nnmail-split-fancy} split, in which the @var{FIELD} is @samp{any},
-the @var{VALUE} is a single regular expression that matches
-@var{to-list}, @var{to-address}, all of @var{extra-aliases} and all
-matches of @var{split-regexp}, and the @var{SPLIT} is the name of the
-group. @var{RESTRICT}s are also supported: just set the
-@var{split-exclude} parameter to a list of regular expressions.
-
-If you can't get the right split to be generated using all these
-parameters, or you just need something fancier, you can set the
-parameter @var{split-spec} to an @code{nnmail-split-fancy} split. In
-this case, all other aforementioned parameters will be ignored by
-@code{gnus-group-split}. In particular, @var{split-spec} may be set to
-@code{nil}, in which case the group will be ignored by
-@code{gnus-group-split}.
+\e$B$?!<$/$5$s$N%a!<%j%s%0%j%9%H$r9XFI$7$F$$$k$1$l$I!"<j$G%a!<%kJ,3d5,B'$r0]\e(B
+\e$B;}$7$?$/$J$$$H$-$O!"%0%k!<%W%a!<%kJ,3d$H$$$&$b$N$,$"$J$?$N$?$a$K$"$j$^$9!#\e(B
+\e$B%0%k!<%W%Q%i%a!<%?$+%0%k!<%W%+%9%?%^%$%:$G\e(B @var{to-list}\e$B!"\e(B
+@var{to-address} \e$B$NN>J}$b$7$/$O$I$A$i$+$r@_Dj$7$F\e(B
+@code{nnmail-split-methods} \e$B$r\e(B @code{gnus-group-split} \e$B$K@_Dj$9$k$@$1$G\e(B
+\e$B$9!#J,3d4X?t$OA4$F$N%0%k!<%W$G$3$l$i$N%Q%i%a!<%?$rAv::$7!"$=$l$K=>$C$FJ,\e(B
+\e$B3d$7$^$9!#$9$J$o$A!"%a!<%k%0%k!<%W$N%Q%i%a!<%?\e(B @var{to-list} \e$B$+\e(B
+@var{to-address} \e$B$G;XDj$5$l$?%"%I%l%9$+$iEj9F$5$l$?$b$N$+!"$=$N%"%I%l%9\e(B
+\e$B$XEj9F$5$l$?%a%C%;!<%8$,$=$N%0%k!<%W$KJ]B8$5$l$^$9!#\e(B
+
+\e$B$H$-$K$O!"%a!<%j%s%0%j%9%H$K$OJ#?t$N%"%I%l%9$,$"$j!"%a!<%kJ,3d$K$=$l$iA4\e(B
+\e$B$F$rG'<1$5$;$?$$$H;W$&$H$-$,$"$k$+$b$7$l$^$;$s\e(B: @var{extra-aliases} \e$B%0%k!<\e(B
+\e$B%W%Q%i%a!<%?$rDI2C$N%"%I%l%9$N%j%9%H$K@_Dj$9$k$@$1$G=*$j$G$9!#@55,I=8=$r\e(B
+\e$B;H$$$?$1$l$P!"\e(B@var{split-regexp} \e$B$r@_Dj$7$F$/$@$5$$!#\e(B
+
+\e$B$3$l$i$NA4$F$N%0%k!<%W$N%Q%i%a!<%?$O!"\e(B@code{nnmail-split-fancy} \e$BJ,3d$r:n\e(B
+\e$B@.$9$k$?$a$K;HMQ$5$l!"$=$l$O\e(B @var{FIELD} \e$B$,\e(B @samp{any} \e$B$G!"\e(B@var{VALUE}
+\e$B$,\e(B@var{to-list}, @var{to-address}, @var{extra-aliases} \e$B$NA4$F!"\e(B
+@var{split-regexp} \e$B$NA4$F$N9gCW$K9gCW$9$kC1FH$N@55,I=8=!"\e(B@var{SPLIT} \e$B$,\e(B
+\e$B%0%k!<%W$NL>A0$K$J$j$^$9!#\e(B@var{RESTRICT} \e$B$b;HMQ$G$-$^$9\e(B:
+@var{split-exclude} \e$B%Q%i%a!<%?$r@55,I=8=$N%j%9%H$K@_Dj$9$k$@$1$G$9!#\e(B
+
+\e$B$3$l$i$NA4$F$N%Q%i%a!<%?$r;H$C$F@5$7$$J,3d$,@8@.$5$l$J$$$H$-$d!"2?$+0c$C\e(B
+\e$B$?$b$N$,I,MW$J$H$-$O!"%Q%i%a!<%?\e(B @var{split-spec} \e$B$r\e(B
+@code{nnmail-split-fancy} \e$BJ,3d$K@_Dj$9$k$3$H$,$G$-$^$9!#$3$N>l9g$O!"B>$N\e(B
+\e$BA0$K=q$$$?A4$F$N%Q%i%a!<%?$O\e(B @code{gnus-group-split} \e$B$KL5;k$5$l$^$9!#FC\e(B
+\e$B$K!"\e(B@var{split-spec} \e$B$O\e(B @code{nil} \e$B$K@_Dj$9$k$3$H$,$G$-!"$=$N>l9g$O%0%k!<\e(B
+\e$B%W$O\e(B @code{gnus-group-split} \e$B$KL5;k$5$l$^$9!#\e(B
@vindex gnus-group-split-default-catch-all-group
-@code{gnus-group-split} will do cross-posting on all groups that match,
-by defining a single @code{&} fancy split containing one split for each
-group. If a message doesn't match any split, it will be stored in the
-group named in @code{gnus-group-split-default-catch-all-group}, unless
-some group has @var{split-spec} set to @code{catch-all}, in which case
-that group is used as the catch-all group. Note that, in this case,
-there's no cross-posting, as a @code{|} fancy split encloses the
-@code{&} split and the catch-all group.
-
-It's time for an example. Assume the following group parameters have
-been defined:
+@code{gnus-group-split} \e$B$O$=$l$>$l$N%0%k!<%W$K0l$D$NJ,3d$r4^$`C10l$N\e(B
+@code{&} \e$BFC5iJ,3d$rDj5A$9$k$3$H$G9gCW$9$kA4$F$N%0%k!<%W$KAj8_Ej9F$r$7$^\e(B
+\e$B$9!#%a%C%;!<%8$,$I$NJ,3d$K$b9gCW$7$J$1$l$P!"$I$l$+$N%0%k!<%W$G\e(B
+@var{split-spec} \e$B$,\e(B @code{catch-all} \e$B$K@_Dj$5$l$F$$$J$$>l9g$O\e(B
+@code{gnus-group-split-default-catch-all-group} \e$B$G;XDj$5$l$F$$$k%0%k!<%W\e(B
+\e$B$KJ]B8$5$l$^$9!#\e(B@var{split-spec} \e$B$,\e(B @code{catch-all} \e$B$K@_Dj$5$l$F$$$k%0\e(B
+\e$B%k!<%W$,$"$k>l9g$O!"$=$N%0%k!<%W$,A4$F$rJa3M$9$k%0%k!<%W$H$7$F;HMQ$5$l$^\e(B
+\e$B$9!#$3$N>l9g$O!"\e(B@code{|} \e$BFC5iJ,3d$,\e(B @code{&} \e$BJ,3d$HA4$F$rJa3M$9$k%0%k!<\e(B
+\e$B%W$rJDJq$9$k$h$&$K!"Aj8_Ej9F$O9T$o$l$J$$$3$H$KCm0U$7$F$/$@$5$$!#\e(B
+
+\e$B$=$m$=$mNc$r=P$9$Y$-$G$7$g$&!#0J2<$N%0%k!<%W%Q%i%a!<%?$,Dj5A$5$l$F$$$k$H\e(B
+\e$B$7$^$9\e(B:
@example
nnml:mail.bar:
((split-spec . catch-all))
@end example
-Setting @code{nnmail-split-methods} to @code{gnus-group-split} will
-behave as if @code{nnmail-split-fancy} had been selected and variable
-@code{nnmail-split-fancy} had been set as follows:
+@code{nnmail-split-methods} \e$B$r\e(B @code{gnus-group-split} \e$B$K@_Dj$9$k$H!"\e(B
+@code{nnmail-split-fancy} \e$B$,A*Br$5$l$F!"JQ?t\e(B @code{nnmail-split-fancy}
+\e$B$,0J2<$N$h$&$K@_Dj$5$l$F$$$k$+$N$h$&$K?6Iq$$$^$9\e(B:
@lisp
(| (& (any "\\(bar@@femail\\.com\\|.*@@femail\\.com\\)" "mail.bar")
@end lisp
@findex gnus-group-split-fancy
-If you'd rather not use group splitting for all your mail groups, you
-may use it for only some of them, by using @code{nnmail-split-fancy}
-splits like this:
+\e$BA4$F$N%a!<%k%0%k!<%W$G%0%k!<%WJ,3d$r;HMQ$7$?$/$O$J$$$H$-$O!"\e(B
+@code{nnmail-split-fancy} \e$BJ,3d$r<!$N$h$&$K;HMQ$9$k$3$H$G$$$/$D$+$N%0%k!<\e(B
+\e$B%W$@$1$K;H$&$3$H$,$G$-$^$9!#\e(B
@lisp
(: gnus-mlsplt-fancy GROUPS NO-CROSSPOST CATCH-ALL)
@end lisp
-@var{GROUPS} may be a regular expression or a list of group names whose
-parameters will be scanned to generate the output split.
-@var{NO-CROSSPOST} can be used to disable cross-posting; in this case, a
-single @code{|} split will be output. @var{CATCH-ALL} may be the name
-of a group to be used as the default catch-all group. If
-@var{CATCH-ALL} is @code{nil}, or if @var{SPLIT-REGEXP} matches the
-empty string in any selected group, no catch-all split will be issued.
-Otherwise, if some group has @var{SPLIT-SPEC} set to @code{catch-all},
-this group will override the value of the @var{CATCH-ALL} argument.
+@var{GROUPS} \e$B$O=PNO$NJ,3d$r@8@.$9$k$?$a$K%Q%i%a!<%?$,Av::$5$l$k%0%k!<%W\e(B
+\e$BL>$N%j%9%H$+@55,I=8=$G$9!#\e(B@var{NO-CROSSPOST} \e$B$OAj8_Ej9F$r;HMQ6X;_$K$k$?\e(B
+\e$B$a$K;H$&$3$H$,$G$-$^$9!#$=$N>l9g!"C10l$N\e(B @code{|} \e$BJ,3d$,=PNO$5$l$^$9!#\e(B
+@var{CATCH-ALL} \e$B$O=i4|A4Ja3M%0%k!<%W$H$7$F;HMQ$5$l$k%0%k!<%WL>$G$9!#\e(B
+@var{CATCH-ALL} \e$B$,\e(B @code{nil} \e$B$G$"$k$+!"\e(B@var{SPLIT-REGEXP} \e$B$,$I$l$+$NA*\e(B
+\e$BBr$5$l$?%0%k!<%W6uJ8;zNs$K9gCW$9$k$H!"A4Ja3MJ,3d$O9T$o$l$^$;$s!#$=$&$G$J\e(B
+\e$B$$>l9g!"%0%k!<%W$K\e(B @var{SPLIT-SPEC} \e$B$,\e(B @code{catch-all} \e$B$K@_Dj$5$l$F$$$k\e(B
+\e$B$b$N$,$"$k$H!"$3$N%0%k!<%W$,\e(B @var{CATCH-ALL} \e$B0z?t$r>e=q$-$7$^$9!#\e(B
@findex gnus-group-split-setup
-Unfortunately, scanning all groups and their parameters can be quite
-slow, especially considering that it has to be done for every message.
-But don't despair! The function @code{gnus-group-split-setup} can be
-used to select @code{gnus-group-split} in a much more efficient way. It
-sets @code{nnmail-split-methods} to @code{nnmail-split-fancy} and sets
-@code{nnmail-split-fancy} to the split produced by
-@code{gnus-group-split-fancy}. Thus, the group parameters are only
-scanned once, no matter how many messages are split.
+\e$BIT1?$J$3$H$K!"A4$F$N%0%k%W$H%Q%i%a!<%?$rAv::$9$k$3$H$OHs>o$KCY$$$G$9!#FC\e(B
+\e$B$KA4$F$N%a%C%;!<%8$KBP$7$F$J$5$l$k$3$H$r9M$($k$H!#$1$l$I$b!"@dK>$7$J$$$G\e(B!
+\e$B4X?t\e(B @code{gnus-group-split-setup} \e$B$,\e(B @code{gnus-group-split} \e$B$r$h$j$:$C\e(B
+\e$B$H8zN(E*$JJ}K!$GA*Br$9$k$h$&$K;H$&$3$H$,$G$-$^$9!#$=$l$O\e(B
+@code{nnmail-split-methods} \e$B$r\e(B @code{nnmail-split-fancy} \e$B$K@_Dj$7!"\e(B
+@code{nnmail-split-fancy} \e$B$r\e(B @code{gnus-group-split-fancy} \e$B$G@8@.$5$l$?\e(B
+\e$BJ,3d$K@_Dj$7$^$9!#$3$&$7$F$I$s$J$KJ,3d$9$k%a%C%;!<%8$,$?$/$5$s$"$C$F$b!"\e(B
+\e$B%0%k!<%W%Q%i%a!<%?$O0lEY$@$1Av::$5$l$^$9!#\e(B
@findex gnus-group-split-update
-However, if you change group parameters, you have to update
-@code{nnmail-split-fancy} manually. You can do it by running
-@code{gnus-group-split-update}. If you'd rather have it updated
-automatically, just tell @code{gnus-group-split-setup} to do it for
-you. For example, add to your @file{.gnus}:
+\e$B$7$+$7!"%0%k!<%W%Q%i%a!<%?$rJQ99$9$k$H!"\e(B@code{nnmail-split-fancy} \e$B$r<j$G\e(B
+\e$B99?7$7$J$1$l$P$J$j$^$;$s!#\e(B@code{gnus-group-split-update} \e$B$r<B9T$9$k$3$H\e(B
+\e$B$G$=$l$r9T$($^$9!#<+F0E*$K99?7$5$l$kJ}$,9%$_$J$i!"\e(B
+@code{gnus-group-split-setup} \e$B$K$=$l$r<B9T$9$k$h$&$K65$($k$@$1$G$9!#Nc$(\e(B
+\e$B$P!"\e(B@file{.gnus} \e$B$K0J2<$N$b$N$rDI2C$7$F$/$@$5$$\e(B:
@lisp
(gnus-group-split-setup AUTO-UPDATE CATCH-ALL)
@end lisp
-If @var{AUTO-UPDATE} is non-@code{nil}, @code{gnus-group-split-update}
-will be added to @code{nnmail-pre-get-new-mail-hook}, so you won't ever
-have to worry about updating @code{nnmail-split-fancy} again. If you
-don't omit @var{CATCH-ALL} (it's optional),
-@code{gnus-group-split-default-catch-all-group} will be set to its
-value.
+@var{AUTO-UPDATE} \e$B$,\e(B @code{nil} \e$B$GL5$$$H!"\e(B@code{gnus-group-split-update}
+\e$B$,\e(B @code{nnmail-pre-get-new-mail-hook} \e$B$KDI2C$5$l!"FsEY$H\e(B
+@code{nnmail-split-fancy} \e$B$N99?7$r?4G[$9$kI,MW$O$"$j$^$;$s!#\e(B
+@var{CATCH-ALL} \e$B$r>JN,$7$J$$>l9g$O\e(B (\e$B$=$l$O%*%W%7%g%s$G$9\e(B)
+@code{gnus-group-split-default-catch-all-group} \e$B$O$=$NCM$K@_Dj$5$l$^$9!#\e(B
@vindex gnus-group-split-updated-hook
-Because you may want to change @code{nnmail-split-fancy} after it is set
-by @code{gnus-group-split-update}, this function will run
-@code{gnus-group-split-updated-hook} just before finishing.
+@code{nnmail-split-fancy} \e$B$,\e(B @code{gnus-group-split-update} \e$B$G@_Dj$5$l$?\e(B
+\e$B8e$K!"JQ99$7$?$$$H$-$N$?$a$K!"$3$N4X?t$O\e(B
+@code{gnus-group-split-update-hook} \e$B$r=*N;$9$kD>A0$K<B9T$7$^$9!#\e(B
@node Incorporating Old Mail
@subsection \e$B8E$$%a!<%k$r<h$j9~$`\e(B
@end lisp
@c TRANSLATEME
-This can also be done non-destructively with
-@code{gnus-list-identifiers}, @xref{Article Hiding}.
+\e$B$3$l$O\e(B @code{gnus-list-identifiers} \e$B$GHsGK2uE*$K9T$&$3$H$b$G$-$^$9!#\e(B
+@xref{Article Hiding}\e$B!#\e(B
@item nnmail-remove-tabs
@findex nnmail-remove-tabs
\e$B2<$5$$!#\e(B
@item
-Fran\e,Ag\e(Bois Pinard---\e$BB?$/$N!"B?$/$N6=L#?<$/40A4$J%P%0%l%]!<%H$H\e(B autoconf \e$B$N\e(B
+Fran\eNgois Pinard---\e$BB?$/$N!"B?$/$N6=L#?<$/40A4$J%P%0%l%]!<%H$H\e(B autoconf \e$B$N\e(B
\e$B%5%]!<%H!#\e(B
@end itemize
Christopher Davis,
Andrew Eskilsson,
Kai Grossjohann,
-David K\e,Ae\e(Bgedal,
+David K\eNegedal,
Richard Pieri,
Fabrice Popineau,
Daniel Quinlan,
Richard Hoskins,
Brad Howes,
Miguel de Icaza,
-Fran\e,Ag\e(Bois Felix Ingrand,
+Fran\eNgois Felix Ingrand,
Tatsuya Ichikawa, @c ?
Ishikawa Ichiro, @c Ishikawa
Lee Iverson,
@end example
@item
- tanken var at n\e,Ae\e(Br du bruker `gnus-startup-file' som prefix (FOO) til \e,Ae\e(B lete
-opp en fil FOO-SERVER, FOO-SERVER.el, FOO-SERVER.eld, kan du la den v\e,Af\e(Bre en
+ tanken var at n\eNer du bruker `gnus-startup-file' som prefix (FOO) til \eNe lete
+opp en fil FOO-SERVER, FOO-SERVER.el, FOO-SERVER.eld, kan du la den v\eNfre en
liste hvor du bruker hvert element i listen som FOO, istedet. da kunne man
hatt forskjellige serveres startup-filer forskjellige steder.
for sci? first the sci.something? then sci.somethingelse?...
@item
-Ja, det burde v\e,Af\e(Bre en m\e,Ae\e(Bte \e,Ae\e(B si slikt. Kanskje en ny variabel?
-`gnus-use-few-score-files'? S\e,Ae\e(B kunne score-regler legges til den
+Ja, det burde v\eNfre en m\eNete \eNe si slikt. Kanskje en ny variabel?
+`gnus-use-few-score-files'? S\eNe kunne score-regler legges til den
"mest" lokale score-fila. F. eks. ville no-gruppene betjenes av
"no.all.SCORE", osv.
@item
gnus-article-hide-pgp
-Selv ville jeg nok ha valgt \e,Ae\e(B slette den dersom teksten matcher
+Selv ville jeg nok ha valgt \eNe slette den dersom teksten matcher
@example
"\\(This\s+\\)?[^ ]+ has been automatically signed by"
@end example
projects / elisp / gnus.git- / commitdiff