From: Richard Riley <rileyrg@googlemail.com>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: ding@gnus.org
Subject: Re: Head. Wall. Bang. (imap fancy splitting)
Date: Tue, 21 Dec 2010 12:24:51 +0100 [thread overview]
Message-ID: <9d4oa7jrlo.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m2d3ovvl86.fsf@verilab.com> (Tommy Kelly's message of "Mon, 20 Dec 2010 21:49:29 -0600")
Tommy Kelly <tommy.kelly@verilab.com> writes:
> Tommy Kelly <tommy.kelly@verilab.com> writes:
>
>> 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"))
>
>> 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"?
>
> I just tested this and the answer appears to be "no". Which raises two
> questions:
>
> 1. If the name of the fancy split variable *is* significant, then why
> did nnmail-split-fancy work when clearly I'm splitting nnimap?
>
> 2. Given that there's only one nnmail-fancy-split variable (or
> nnimap-fancy-split). if there are multiple secondary servers, how do you
> control their splitting separately?
>
This is the thing that confuses me with the elisp part.
The call to ...-secondary-methods creates a server local version of the
nnmail-split-methods as far as I know. So each server has its own
version. And why, in elisp, when you examine a variable you need to be
sure of the context. Its probably not the value gnus sees when
processing that group. I asked a Q about this a few months ago too. Also
notice the lack of a quote on the nnimap-split-methods assignment.
next prev parent reply other threads:[~2010-12-21 11:24 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
2010-12-21 3:49 ` Tommy Kelly
2010-12-21 11:24 ` Richard Riley [this message]
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=9d4oa7jrlo.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
--cc=tommy.kelly@verilab.com \
/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).