From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: ding@gnus.org
Subject: Re: per group split rules
Date: Mon, 08 Nov 2021 22:38:31 +0000 [thread overview]
Message-ID: <87lf1yp920.fsf@gnus.jao.io> (raw)
In-Reply-To: <87wnli2w7n.fsf@zoho.eu>
On Mon, Nov 08 2021, Emanuel Berg wrote:
> Jose A. Ortega Ruiz wrote:
>
>> i have my mail-sources set to '((group)), so that each of my
>> nnml groups has a mail-source of its own (typically reading
>> a spool file or a local maildir, populated asynchronously).
>> is there a way of having split rules (fancy or not) that
>> apply /only/ to a given nnml group, rather than globally to
>> all incoming mail?
>
> Respooling perhaps ... how often/when is this supposed
> to happen?
every time i import new mail, so i think that's not going to be
practical.
>> or, alternatively, is it possible to have a (global) split
>> rule that says (when nnmail-resplit-incoming is t) something
>> like: "leave this message in the group which fetched it via
>> its mail-source parameter"?
>
> You can use functions instead of regexps both with fancy and
> regular so put it there if so, I guess?
yes, one of my first thoughts, but when a splitting function is called,
the incoming mail has been inserted in a temp current buffer and there
seems to be no way of knowing what its original mail-source was (but i
have to try again and check the value of that variable, maybe it's still
set... i am not sure i tried that).
thanks,
jao
--
Besides the noble art of getting things done, there is the noble art
of leaving things undone. The wisdom of life consists in the
elimination of nonessentials.
-Lin Yutang, writer and translator (1895-1976)
next prev parent reply other threads:[~2021-11-08 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 19:16 Jose A. Ortega Ruiz
2021-11-08 21:06 ` Emanuel Berg
2021-11-08 22:38 ` Jose A. Ortega Ruiz [this message]
2021-11-08 23:46 ` Emanuel Berg
2021-11-08 23:21 ` Jose A. Ortega Ruiz
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=87lf1yp920.fsf@gnus.jao.io \
--to=jao@gnu.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).