From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: group splitting and gnus-secondary-select-methods
Date: Sat, 12 Aug 2017 20:01:01 -0700 [thread overview]
Message-ID: <87a834goia.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87valut0l1.fsf@grothesque.org>
Christoph Groth <christoph@grothesque.org> writes:
> Eric, Emanuel,
>
> Thank you for the quick replies! Perhaps I haven't been clear: when I
> said that I'm trying to setup "group mail splitting" I didn't mean
> plain mail splitting (I have been using that one since the begin of
> the century or so), I meant what the Gnus manual calls "group mail
> splitting" (there's a section on it). Gnus has functionality to
> generate fancy splitting rules automatically for groups that contain
> 'to-list' or 'to-address' parameters. If you have defined these
> parameters for some groups and evaluate (gnus-group-split-fancy),
> you'll get a split that can be assigned to the variable
> nnimap-split-fancy.
Oh... that's something I haven't used before, sorry.
Are you using it as directed, as an element of `nnmail-split-fancy'?
Simply calling it in your gnus file isn't going to produce the correct
results, the function needs to be a part of that variable's value to do
the right thing.
If that doesn't work, try putting (gnus-group-split-setup t) in your
gnus file? That looks like it will set up the correct hooks for
updating.
Like I said, I haven't used this before, and the above suggestions just
come from a brief perusal of gnus-mlspl.el. Apologies if you've already
gone through that file and these approaches haven't worked...
Eric
next prev parent reply other threads:[~2017-08-13 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 22:47 Christoph Groth
2017-08-11 16:22 ` Eric Abrahamsen
2017-08-11 18:34 ` Christoph Groth
2017-08-13 3:01 ` Eric Abrahamsen [this message]
2017-08-11 16:35 ` Emanuel Berg
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=87a834goia.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.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).