From: Simon Josefsson <jas@extundo.com>
Subject: Re: variables for `nnimap-split-fancy'
Date: Wed, 26 Nov 2003 00:13:56 +0100 [thread overview]
Message-ID: <iluekvwujm3.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m27k1oz5bz.fsf@copernicus.rlent.pnet>
Roland Roberts <roland@astrofoto.org> writes:
> The Gnus docs say you can set nnimap-split-rule to nnmail-split-fancy
> to use the same rule as you did for nnmail. That's a nice option when
> converting, but it has a couple of problems. First, the nnmail groups
> all sit beneath an implied tree but, depending on your imap server,
> the nnimap groups may not (mine don't) and I can't find how to set an
> implied prefix for nnimap groups. Second, there is no mention of
> auxiliary variables; with nnmail, I have several items added to
> nnmail-split-abbrev-alist. Is there an equivalent for nnimap?
> Currently, I just added a (require "nnmail") and use my old
> nnmail-split-abbrev-alist settings.
I think nnimap simply call nnmail-spliy-fancy, so it should use all
the same nnmail variables automatically. But I don't use fancy
splitting myself.
parent reply other threads:[~2003-11-25 23:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m27k1oz5bz.fsf@copernicus.rlent.pnet>]
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=iluekvwujm3.fsf@latte.josefsson.org \
--to=jas@extundo.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).