From: Teemu Likonen <tlikonen@iki.fi>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Gnus manual bug on nnimap splitting?
Date: Sat, 30 Jan 2016 23:23:18 +0200 [thread overview]
Message-ID: <87twlubw3d.fsf@iki.fi> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 654 bytes --]
Hi,
the info node "(gnus) Client-Side IMAP Splitting" says:
‘nnimap-split-methods’
Uses the same syntax as ‘nnmail-split-methods’ [...]
OK, the same syntax as nnmail-split-methods. Then later in the same node
there is an example where the same variable is given a value with
_fancy_ splitting syntax:
(nnimap "imap.example.com"
(nnimap-inbox "INBOX")
(nnimap-split-methods
(| ("MailScanner-SpamCheck" "spam" "spam.detected")
(to "foo@bar.com" "foo")
"undecided")))
Clearly a documentation bug. So maybe:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: Type: text/x-diff, Size: 575 bytes --]
diff --git i/doc/misc/gnus.texi w/doc/misc/gnus.texi
index ab96684..8dd0c1b 100644
--- i/doc/misc/gnus.texi
+++ w/doc/misc/gnus.texi
@@ -14322,13 +14322,13 @@ Client-Side IMAP Splitting
Here's a complete example @code{nnimap} backend with a client-side
``fancy'' splitting method:
@example
(nnimap "imap.example.com"
(nnimap-inbox "INBOX")
- (nnimap-split-methods
+ (nnimap-split-fancy
(| ("MailScanner-SpamCheck" "spam" "spam.detected")
(to "foo@@bar.com" "foo")
"undecided")))
@end example
[-- Attachment #1.3: Type: text/plain, Size: 134 bytes --]
--
/// Teemu Likonen - .-.. <https://github.com/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next reply other threads:[~2016-01-30 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 21:23 Teemu Likonen [this message]
2016-02-04 3:09 ` Gnus manual bug on nnimap splitting? Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twlubw3d.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.