From 606dfb60e38bc3237afaa63cd92ef6b738fd54a1 Mon Sep 17 00:00:00 2001 From: Lars Ingebrigtsen Date: Fri, 21 Jan 2022 12:48:03 +0100 Subject: [PATCH] Clarify Splitting Mail in the Gnus manual * doc/misc/gnus.texi (Splitting Mail): Clarify what happens when crossposting or not (bug#53307). --- doc/misc/gnus.texi | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi index b3efdfbacba..306d66de64e 100644 --- a/doc/misc/gnus.texi +++ b/doc/misc/gnus.texi @@ -14838,12 +14838,17 @@ mail belongs in that group. The last of these groups should always be a general one, and the regular expression should @emph{always} be @samp{""} so that it matches any mails that haven't been matched by any of the other regexps. (These rules are -processed from the beginning of the alist toward the end. The first rule -to make a match will ``win'', unless you have crossposting enabled. In -that case, all matching rules will ``win''.) If no rule matched, the mail -will end up in the @samp{bogus} group. When new groups are created by -splitting mail, you may want to run @code{gnus-group-find-new-groups} to -see the new groups. This also applies to the @samp{bogus} group. +processed from the beginning of the alist toward the end. + +If multiple rules match (excluding the general @samp{""} group), mail +is crossposted to all these groups. However, if +@code{nnmail-crosspost} is set to @code{nil}, the first rule to make a +match will ``win''. + +If no rule matched, the mail will end up in the @samp{bogus} group. +When new groups are created by splitting mail, you may want to run +@code{gnus-group-find-new-groups} to see the new groups. This also +applies to the @samp{bogus} group. If you like to tinker with this yourself, you can set this variable to a function of your choice. This function will be called without any -- 2.39.5