\e$BL$FI!"4{FI5-;v$NN>J}$rA4$FI=<($7$^$9!#\e(B
@item an integer
-\e$B$=$N%0%k!<%W$N:G8e$N@0?t8D$N5-;v$rI=<($7$^$9!#$3$l$O\e(B C-u \e$B@0?t\e(B \e$B$G$=$N%0%k!<\e(B
-\e$B%W$KF~$k$N$HF1$8$G$9!#\e(B
+\e$B$=$N%0%k!<%W$N:G8e$N\e(B @var{integer} \e$B8D$N5-;v$rI=<($7$^$9!#$3$l$O\e(B C-u
+@var{integer} \e$B$G$=$N%0%k!<%W$KF~$k$N$HF1$8$G$9!#\e(B
@item default
\e$B=i4|@_Dj$G$NI=<(5-;v$rI=<($7$^$9!#$3$l$ODL>o$OL$FI5-;v$H0uIU$-5-;v$G$9!#\e(B
@item gnus-article-address-banner-alist
@vindex gnus-article-address-banner-alist
\e$B%a!<%k%"%I%l%9$H%P%J!<$NO"A[%j%9%H$G$9!#$=$l$>$l$NMWAG\e(B
-\e$B$O\e(B @code{(ADDRESS . BANNER)} \e$B$N7A<0$r;}$A!"$3$3$G\e(B ADDRESS \e$B$O\e(B From \e$B%X%C%@!<\e(B
-\e$B$K$"$k%a!<%k%"%I%l%9$K%^%C%A$9$k@55,I=8=!"\e(BBANNER \e$B$O%7%s%\\e(B
-\e$B%k\e(B @code{signature}\e$B!"\e(B@code{gnus-article-banner-alist} \e$B$NMWAG!"@55,I=8=$^\e(B
-\e$B$?$O\e(B @code{nil} \e$B$N$&$A$N0l$D$G$9!#\e(BADDRESS \e$B$,Cx<T$N%a!<%k%"%I%l%9$K%^%C%A\e(B
-\e$B$9$k$H!"9-9p$N$h$&$J$b$N$r>C$7$^$9!#Nc$($P!"Aw?.<T\e(B
-\e$B$,\e(B @samp{hail@@yoo-hoo.co.jp} \e$B$H$$$&%a!<%k%"%I%l%9$r;}$C$F$$$F!"H`$,Aw?.\e(B
-\e$B$9$k$9$Y$F$N5-;v$K\e(B @samp{Do You Yoo-hoo!?} \e$B$N$h$&$J$b$N$,$"$k>l9g!"0J2<\e(B
-\e$B$NMWAG$G$=$l$i$r>C$9$3$H$,$G$-$^$9!#\e(B
+\e$B$O\e(B @code{(@var{address} . @var{banner})} \e$B$N7A<0$r;}$A!"$3$3\e(B
+\e$B$G\e(B @var{address} \e$B$O\e(B From \e$B%X%C%@!<$K$"$k%a!<%k%"%I%l%9$K%^%C%A$9$k@55,I=\e(B
+\e$B8=!"\e(B@var{banner} \e$B$O%7%s%\%k\e(B @code{signature}\e$B!"\e(B
+@code{gnus-article-banner-alist} \e$B$NMWAG!"@55,I=8=$^$?$O\e(B @code{nil} \e$B$N$&\e(B
+\e$B$A$N0l$D$G$9!#\e(B@var{address} \e$B$,Cx<T$N%a!<%k%"%I%l%9$K%^%C%A$9$k$H!"9-9p$N\e(B
+\e$B$h$&$J$b$N$r>C$7$^$9!#Nc$($P!"Aw?.<T$,\e(B @samp{hail@@yoo-hoo.co.jp} \e$B$H$$$&\e(B
+\e$B%a!<%k%"%I%l%9$r;}$C$F$$$F!"H`$,Aw?.$9$k$9$Y$F$N5-;v$K\e(B @samp{Do You
+Yoo-hoo!?} \e$B$N$h$&$J$b$N$,$"$k>l9g!"0J2<$NMWAG$G$=$l$i$r>C$9$3$H$,$G$-$^\e(B
+\e$B$9!#\e(B
@lisp
("@@yoo-hoo\\.co\\.jp\\'" . "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
@item to-address
@code{To} \e$BMs$,8=:_$N%0%k!<%W$N\e(B @code{to-address} \e$B%Q%i%a!<%?$HF1$8$b$N$7\e(B
\e$B$+4^$s$G$$$J$$>l9g$K$O>C5n$7$^$9!#\e(B
+@item to-list
+@code{To} \e$BMs$,8=:_$N%0%k!<%W$N\e(B @code{to-list} \e$B%Q%i%a!<%?$HF1$8$b$N$7$+4^\e(B
+\e$B$s$G$$$J$$>l9g$K$O>C5n$7$^$9!#\e(B
+@item cc-list
+@code{CC} \e$BMs$,8=:_$N%0%k!<%W$N\e(B @code{to-list} \e$B%Q%i%a!<%?$HF1$8$b$N$7$+4^\e(B
+\e$B$s$G$$$J$$>l9g$K$O>C5n$7$^$9!#\e(B
@item date
\e$B$=$N5-;v$,2a5n;0F|0JFb$N$b$N$G$"$l$P!"\e(B@code{Date} \e$BMs$r>C5n$7$^$9!#\e(B
@item long-to
@item gnus-score-file-suffix
@vindex gnus-score-file-suffix
\e$B%9%3%"%U%!%$%k$K$?$I$jCe$/$?$a$K%0%k!<%WL>$K2C$($k@\Hx8l$G$9\e(B (\e$B=i4|CM\e(B
-\e$B$G\e(B @samp{SCORE} \e$B$G$9!#\e(B)
+\e$B$G\e(B @file{SCORE} \e$B$G$9!#\e(B)
@item gnus-score-uncacheable-files
@vindex gnus-score-uncacheable-files
@vindex gnus-adaptive-file-suffix
\e$BE,1~@-%9%3%"EPO?9`L\$O!"%0%k!<%WL>$K\e(B @code{gnus-adaptive-file-suffix} \e$B$r\e(B
-\e$BIU2C$7$?L>A0$N%U%!%$%k$KF~$l$i$l$^$9!#=i4|@_DjCM$O\e(B @samp{ADAPT} \e$B$G$9!#\e(B
+\e$BIU2C$7$?L>A0$N%U%!%$%k$KF~$l$i$l$^$9!#=i4|@_DjCM$O\e(B @file{ADAPT} \e$B$G$9!#\e(B
@vindex gnus-score-exact-adapt-limit
\e$BE,1~@-%9%3%"$r9T$&$H$-$O!"ItJ,J8;zNs0lCW$d%U%!%8!<$J0lCW$r9T$C$?J}$,!"$*\e(B
@item hashcash-payment-alist
@vindex hashcash-payment-alist
\e$B2??M$+$N<u<h?M$O!"$"$J$?$K%G%#%U%)%k%H$h$jB?$/$N\e(B CPU \e$B;~4V$rHq$d$9$3$H$r\e(B
-\e$BMW5a$9$k$+$b$7$l$^$;$s!#$3$NJQ?t$O\e(B @samp{(ADDR AMOUNT)} \e$B$N7A<0$NMWAG$N%j\e(B
-\e$B%9%H$G!"\e(BADDR \e$B$O<u<h?M\e(B (\e$B%a!<%k%"%I%l%9$+%K%e!<%9%0%k!<%W\e(B)\e$B!"\e(BAMOUNT \e$B$OI,MW\e(B
-\e$B$H$5$l$k>WFM$N%S%C%H?t$G$9!#$3$l$O$^$?\e(B @samp{(ADDR STRING AMOUNT)} \e$B$NMW\e(B
-\e$BAG$r;}$D$3$H$b2DG=$G!"\e(BSTRING \e$B$OJ8;zNs\e(B (\e$BDL>o$O%a!<%k%"%I%l%9$+%K%e!<%9%0\e(B
-\e$B%k!<%WL>\e(B) \e$B$H$7$F;H$o$l$^$9!#\e(B
+\e$BMW5a$9$k$+$b$7$l$^$;$s!#$3$NJQ?t$O\e(B @samp{(@var{addr} @var{amount})} \e$B$N7A\e(B
+\e$B<0$NMWAG$N%j%9%H$G!"\e(B@var{addr} \e$B$O<u<h?M\e(B (\e$B%a!<%k%"%I%l%9$+%K%e!<%9%0%k!<\e(B
+\e$B%W\e(B)\e$B!"\e(B@var{amount} \e$B$OI,MW$H$5$l$k>WFM$N%S%C%H?t$G$9!#$3$l$O$^\e(B
+\e$B$?\e(B @samp{(@var{addr} @var{string} @var{amount})} \e$B$NMWAG$r;}$D$3$H$b2DG=\e(B
+\e$B$G!"\e(B@var{string} \e$B$OJ8;zNs\e(B (\e$BDL>o$O%a!<%k%"%I%l%9$+%K%e!<%9%0%k!<%WL>\e(B) \e$B$H\e(B
+\e$B$7$F;H$o$l$^$9!#\e(B
@item hashcash
@vindex hashcash
Display all articles, both read and unread.
@item an integer
-Display the last INTEGER articles in the group. This is the same as
-entering the group with C-u INTEGER.
+Display the last @var{integer} articles in the group. This is the same as
+entering the group with C-u @var{integer}.
@item default
Display the default visible articles, which normally includes unread and
@item gnus-article-address-banner-alist
@vindex gnus-article-address-banner-alist
Alist of mail addresses and banners. Each element has the form
-@code{(ADDRESS . BANNER)}, where ADDRESS is a regexp matching a mail
-address in the From header, BANNER is one of a symbol @code{signature},
-an item in @code{gnus-article-banner-alist}, a regexp and @code{nil}.
-If ADDRESS matches author's mail address, it will remove things like
-advertisements. For example, if a sender has the mail address
-@samp{hail@@yoo-hoo.co.jp} and there is a banner something like
-@samp{Do You Yoo-hoo!?} in all articles he sends, you can use the
-following element to remove them:
+@code{(@var{address} . @var{banner})}, where @var{address} is a regexp
+matching a mail address in the From header, @var{banner} is one of a
+symbol @code{signature}, an item in @code{gnus-article-banner-alist},
+a regexp and @code{nil}. If @var{address} matches author's mail
+address, it will remove things like advertisements. For example, if a
+sender has the mail address @samp{hail@@yoo-hoo.co.jp} and there is a
+banner something like @samp{Do You Yoo-hoo!?} in all articles he
+sends, you can use the following element to remove them:
@lisp
("@@yoo-hoo\\.co\\.jp\\'" . "\n_+\nDo You Yoo-hoo!\\?\n.*\n.*\n")
@item to-address
Remove the @code{To} header if it only contains the address identical to
the current groups's @code{to-address} parameter.
+@item to-list
+Remove the @code{To} header if it only contains the address identical to
+the current groups's @code{to-list} parameter.
+@item cc-list
+Remove the @code{CC} header if it only contains the address identical to
+the current groups's @code{to-list} parameter.
@item date
Remove the @code{Date} header if the article is less than three days
old.
@vindex nnmail-mail-splitting-charset
@vindex nnmail-mail-splitting-decodes
-By default the splitting codes MIME decodes headers so you can match
+By default the splitting codes @sc{mime} decodes headers so you can match
on non-ASCII strings. The @code{nnmail-mail-splitting-charset}
variable specifies the default charset for decoding. The behaviour
can be turned off completely by binding
when the @code{:} function is run.
@item
-@code{(! @var{func} @var{split})}: If the split is a list, and the first
-element is @code{!}, then SPLIT will be processed, and FUNC will be
-called as a function with the result of SPLIT as argument. FUNC should
-return a split.
+@code{(! @var{func} @var{split})}: If the split is a list, and the
+first element is @code{!}, then @var{split} will be processed, and
+@var{func} will be called as a function with the result of @var{split}
+as argument. @var{func} should return a split.
@item
@code{nil}: If the split is @code{nil}, it is ignored.
run through @code{nndoc-unquote-dashes} before being delivered.
To hook your own document definition into @code{nndoc}, use the
-@code{nndoc-add-type} function. It takes two parameters---the first is
-the definition itself and the second (optional) parameter says where in
-the document type definition alist to put this definition. The alist is
-traversed sequentially, and @code{nndoc-TYPE-type-p} is called for a given type @code{TYPE}. So @code{nndoc-mmdf-type-p} is called to see whether a document
-is of @code{mmdf} type, and so on. These type predicates should return
-@code{nil} if the document is not of the correct type; @code{t} if it is
-of the correct type; and a number if the document might be of the
-correct type. A high number means high probability; a low number means
-low probability with @samp{0} being the lowest valid number.
+@code{nndoc-add-type} function. It takes two parameters---the first
+is the definition itself and the second (optional) parameter says
+where in the document type definition alist to put this definition.
+The alist is traversed sequentially, and @code{nndoc-TYPE-type-p} is
+called for a given type @code{TYPE}. So @code{nndoc-mmdf-type-p} is
+called to see whether a document is of @code{mmdf} type, and so on.
+These type predicates should return @code{nil} if the document is not
+of the correct type; @code{t} if it is of the correct type; and a
+number if the document might be of the correct type. A high number
+means high probability; a low number means low probability with
+@samp{0} being the lowest valid number.
@node SOUP
@item gnus-score-file-suffix
@vindex gnus-score-file-suffix
Suffix to add to the group name to arrive at the score file name
-(@samp{SCORE} by default.)
+(@file{SCORE} by default.)
@item gnus-score-uncacheable-files
@vindex gnus-score-uncacheable-files
@cindex score cache
All score files are normally cached to avoid excessive re-loading of
score files. However, if this might make your Emacs grow big and
-bloated, so this regexp can be used to weed out score files unlikely to be needed again. It would be a bad idea to deny caching of
+bloated, so this regexp can be used to weed out score files unlikely
+to be needed again. It would be a bad idea to deny caching of
@file{all.SCORE}, while it might be a good idea to not cache
@file{comp.infosystems.www.authoring.misc.ADAPT}. In fact, this
variable is @samp{ADAPT$} by default, so no adaptive score files will
@vindex gnus-adaptive-file-suffix
The adaptive score entries will be put into a file where the name is the
group name with @code{gnus-adaptive-file-suffix} appended. The default
-is @samp{ADAPT}.
+is @file{ADAPT}.
@vindex gnus-score-exact-adapt-limit
When doing adaptive scoring, substring or fuzzy matching would probably
friends.@footnote{On a GNU/Linux system look for packages with names
like @code{netpbm}, @code{libgr-progs} and @code{compface}.})
-(NOTE: @code{x-face} is used in the variable/function names, not
+(Note: @code{x-face} is used in the variable/function names, not
@code{xface}).
Gnus provides a few convenience functions and variables to allow
@item hashcash-payment-alist
@vindex hashcash-payment-alist
Some receivers may require you to spend burn more CPU time than the
-default. This variable contains a list of @samp{(ADDR AMOUNT)} cells,
-where ADDR is the receiver (email address or newsgroup) and AMOUNT is
-the number of bits in the collision that is needed. It can also
-contain @samp{(ADDR STRING AMOUNT)} cells, where the STRING is the
-string to use (normally the email address or newsgroup name is used).
+default. This variable contains a list of @samp{(@var{addr}
+@var{amount})} cells, where @var{addr} is the receiver (email address
+or newsgroup) and @var{amount} is the number of bits in the collision
+that is needed. It can also contain @samp{(@var{addr} @var{string}
+@var{amount})} cells, where the @var{string} is the string to use
+(normally the email address or newsgroup name is used).
@item hashcash
@vindex hashcash
documented elsewhere, but to get you started there are a few steps
that need to be followed. First, instrument the part of Gnus you are
interested in for profiling, e.g. @kbd{M-x elp-instrument-package RET
-gnus} or @kbd{M-x elp-instrument-packagre RET message}. Then perform
+gnus} or @kbd{M-x elp-instrument-package RET message}. Then perform
the operation that is slow and press @kbd{M-x elp-results}. You will
then see which operations that takes time, and can debug them further.
If the entire operation takes much longer than the time spent in the
projects / elisp / gnus.git- / commitdiff