Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Rene Borchers <rmborchers@gmail.com>
Cc: ding@gnus.org
Subject: Re: splitting not working after update emacs 23.9xxx to 24.0.91.1
Date: Tue, 03 Jan 2012 22:04:52 +0100	[thread overview]
Message-ID: <m3fwfwh4zv.fsf@stories.gnus.org> (raw)
In-Reply-To: <CABRKuPSWRa1eRv-e+D+=DU45ns0FgEpWBV4W84=dAZPjx+r=ag@mail.gmail.com> (Rene Borchers's message of "Fri, 2 Dec 2011 09:17:25 +0100")

Rene Borchers <rmborchers@gmail.com> writes:

> After updating emacs  to a more recent version from git. imap splitting
> stopped working. I have been messing around with replacing
> nnimap-inbox and nnimap-split-inbox in combination with
> nnimap-split-rules and nnimap-split-methods.

(setq nnimap-inbox "INBOX")
(setq nnimap-split-methods ...)

should do the trick.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



      reply	other threads:[~2012-01-03 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  8:17 Rene Borchers
2012-01-03 21:04 ` Lars Magne Ingebrigtsen [this message]

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=m3fwfwh4zv.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=rmborchers@gmail.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).