doc-bug: bogus (and catch-all) group in mail splitting

[Reiner Steib <reinersteib+gmane@imap.cc>]

Hi,

on the occasion of a question in g.e.g [1], I searched for the "bogus"
(created by Gnus' mail splitting when no entry matched) group in the
manual and I didn't find anything.  I think we should add a sentence
on the bogus group.

Additionally, I think it is confusing that the manual says
  »`*'« and »general (`*') group«
in the text for the catch-all group, but in the split code examples
there is
  »("mail.other" "")«.
Shouldn't it be »""« in the text?  Am I missing something?

--8<---------------cut here---------------start------------->8---
--- gnus.texi	15 Oct 2004 21:24:48 +0200	6.603.2.12
+++ gnus.texi	06 Nov 2004 14:29:14 +0100	
@@ -13245,13 +13245,14 @@
 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
+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''.)  When new groups are
-created by splitting mail, you may want to run
-@code{gnus-group-find-new-groups} to see the new groups.
+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.
 
 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
@@ -13268,7 +13269,7 @@
 The mail back ends all support cross-posting.  If several regexps match,
 the mail will be ``cross-posted'' to all those groups.
 @code{nnmail-crosspost} says whether to use this mechanism or not.  Note
-that no articles are crossposted to the general (@samp{*}) group.
+that no articles are crossposted to the general (@samp{""}) group.
 
 @vindex nnmail-crosspost-link-function
 @cindex crosspost
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.

[1] <m31xfa8uzq.fsf@hermes.ekkehard.goerlach.loe>
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/