From: Tommy Kelly <tommy.kelly@verilab.com>
To: ding@gnus.org
Subject: Re: Head. Wall. Bang. (imap fancy splitting)
Date: Mon, 20 Dec 2010 19:38:48 -0600 [thread overview]
Message-ID: <m2hbe7vr9z.fsf@verilab.com> (raw)
In-Reply-To: <87k4j4exl5.fsf@maru.md5i.com>
Michael Welsh Duggan <md5i@md5i.com> writes:
> Try changing to:
> (setq gnus-secondary-select-methods
> '((nnimap "work"
> (nnimap-address "imap.gmail.com")
> (nnimap-stream ssl)
> (nnimap-server-port 993)
> (nnimap-inbox "INBOX")
> (nnimap-split-methods nnmail-split-fancy))))
> (setq nnmail-split-fancy '(| "TEST-GROUP"))
OK, excellent, now we're getting somewhere. Thanks!
Now I notice you used (and I copied you) "nnmail-split-fancy" instead of
"nnimap-split-fancy". Is that because the precise name of that is
arbitrary? Could I call it "fiendishly-difficult-thing-to-grasp"?
If so that would answer my next question which is, how do I have
different fancy split methods for different servers, in the case (like
mine in reality) where there are multiple secondary select methods. Is
it OK to have:
(setq gnus-secondary-select-methods
'(
(nnimap "work"
...
(nnimap-split-methods nnmail-split-fancy-work)
)
(nnimap "home"
...
(nnimap-split-methods nnmail-split-fancy-home)
)
(nnimap "faff"
...
(nnimap-split-methods nnmail-split-fancy-faff)
)
)
)
(setq nnmail-split-fancy-work '(| "TEST-GROUP"))
(setq nnmail-split-fancy-home '(| "TEST-GROUP")) ;; where this is a different TEST-GROUP from the above
(setq nnmail-split-fancy-faff '(| "TEST-GROUP-FAFF"))
Tommy
next prev parent reply other threads:[~2010-12-21 1:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 23:57 Tommy Kelly
2010-12-21 1:14 ` Michael Welsh Duggan
2010-12-21 1:38 ` Tommy Kelly [this message]
2010-12-21 3:49 ` Tommy Kelly
2010-12-21 11:24 ` Richard Riley
2010-12-21 15:26 ` Tommy Kelly
2010-12-21 11:20 ` Richard Riley
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=m2hbe7vr9z.fsf@verilab.com \
--to=tommy.kelly@verilab.com \
--cc=ding@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).