# HG changeset patch # User Dave Love # Date 976793488 0 # Node ID 44a6d536cea30dece21f96256c79ab2e7b7c9f62 # Parent 51be06b616bfe77eaa4f250ee349ab0d38c3346e Changes from Gnus CVS and fixes. diff -r 51be06b616bf -r 44a6d536cea3 man/gnus.texi --- a/man/gnus.texi Thu Dec 14 10:55:36 2000 +0000 +++ b/man/gnus.texi Thu Dec 14 11:31:28 2000 +0000 @@ -364,7 +364,7 @@ spool or your mbox file. All at the same time, if you want to push your luck. -This manual corresponds to Gnus 5.8.7. +This manual corresponds to Gnus 5.9.0. @end ifinfo @@ -8549,7 +8549,9 @@ suggest where to put the articles. @code{gnus-move-split-methods} is a variable that uses the same syntax as @code{gnus-split-methods} (@pxref{Saving Articles}). You may customize that variable to create -suggestions you find reasonable. +suggestions you find reasonable. (Note that +@code{gnus-move-split-methods} uses group names where +@code{gnus-split-methods} uses file names.) @lisp (setq gnus-move-split-methods @@ -10473,12 +10475,13 @@ The file contains one or more line, each of which define one server. @item -Each line may contain an arbitrary number of token/value pairs. The -valid tokens include @samp{machine}, @samp{login}, @samp{password}, -@samp{default}, @samp{port} and @samp{force}. (The latter is not a -valid @file{.netrc}/@code{ftp} token, which is almost the only way the -@file{.authinfo} file format deviates from the @file{.netrc} file -format.) +The valid tokens include @samp{machine}, @samp{login}, @samp{password}, +@samp{default}. In addition Gnus introduces two new tokens, not present +in the original @file{.netrc}/@code{ftp} syntax, namely @samp{port} and +@samp{force}. (This is the only way the @file{.authinfo} file format +deviates from the @file{.netrc} file format.) @samp{port} is used to +indicate what port on the server the credentials apply to and +@samp{force} is explained below. @end enumerate @@ -11764,8 +11767,12 @@ When it has found a parent, it returns the corresponding group name. It is recommended that you set @code{nnmail-message-id-cache-length} to a somewhat higher number than the default so that the message ids are -still in the cache. (A value of 5000 appears to create a file some -300 kBytes in size.) +still in the cache. (A value of 5000 appears to create a file some 300 +kBytes in size.) +@vindex nnmail-cache-accepted-message-ids +When @code{nnmail-cache-accepted-message-ids} is non-@code{nil}, Gnus +also records the message ids of moved articles, so that the followup +messages goes into the new group. @node Group Mail Splitting @@ -11810,9 +11817,13 @@ 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. +that group is used as the catch-all group. Even though this variable is +often used just to name a group, it may also be set to an arbitrarily +complex fancy split (after all, a group name is a fancy split), and this +may be useful to split mail that doesn't go to any mailing list to +personal mail folders. Note that this fancy split is added as the last +element of a @code{|} split list that also contains a @code{&} split +with the rules extracted from group parameters. It's time for an example. Assume the following group parameters have been defined: @@ -11853,9 +11864,9 @@ @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 +single @code{|} split will be output. @var{catch-all} is the fallback +fancy split, used like @var{gnus-group-split-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. @@ -11864,7 +11875,7 @@ 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 +used to enable @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 @@ -11884,7 +11895,7 @@ 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), +don't omit @var{catch-all} (it's optional, equivalent to @code{nil}), @code{gnus-group-split-default-catch-all-group} will be set to its value.