From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: latest sources do not client-split IMAP anymore
Date: Wed, 15 Dec 2010 20:24:46 +0100 [thread overview]
Message-ID: <m3oc8mq1oh.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87fwtz4vfj.fsf@pcuds33.cern.ch>
Tibor Simko <tibor.simko@cern.ch> writes:
> It's due to recent changes in `gnus-setup-news'. The attached patch
> fixes things for me.
[...]
> + (gnus-read-active-file nil dont-connect))
So reading the active file(s) makes nnimap split its mail for you, while
nothing else does this? That's odd... hm...
If you eval this
(gnus-read-active-file nil nil)
is IMAP mail split?
I'm unable to reproduce the problem with git Gnus.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-15 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 18:33 Tibor Simko
2010-12-14 22:29 ` Lars Magne Ingebrigtsen
2010-12-15 2:33 ` Tibor Simko
2010-12-15 19:24 ` Lars Magne Ingebrigtsen [this message]
2010-12-15 21:11 ` Tibor Simko
2010-12-16 16:13 ` Lars Magne Ingebrigtsen
2010-12-16 17:21 ` Tibor Simko
2010-12-16 17:25 ` Lars Magne Ingebrigtsen
2010-12-16 21:39 ` Tibor Simko
2010-12-18 20:19 ` Richard Riley
2010-12-20 23:55 ` Tibor Simko
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=m3oc8mq1oh.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).