Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: Re: per group split rules
Date: Tue, 09 Nov 2021 00:46:28 +0100	[thread overview]
Message-ID: <87fss62otn.fsf@zoho.eu> (raw)
In-Reply-To: <87lf1yp920.fsf@gnus.jao.io>

Jose A. Ortega Ruiz wrote:

> 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).

So you are sorting based on something that has happened yet
didn't leave a trace?

Maybe you can tell it to add a header just telling?

Then you can split on that super-easy with a regexp, no need
for a function.

-- 
underground experts united
https://dataswamp.org/~incal



  reply	other threads:[~2021-11-08 23:47 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
2021-11-08 23:46     ` Emanuel Berg [this message]
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=87fss62otn.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --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).