discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 0/3] inject: Add support for skipping messages
Date: Sat, 22 Aug 2020 15:01:27 -0400	[thread overview]
Message-ID: <20200822190130.20397-1-kyle@kyleam.com> (raw)

When I'm using Gnus to read a thread via nntp and decide I want it in
my regular mail (notmuch), I call piem-inject-thread-into-maildir to
pull the thread into my notmuch database.  If I call it again at a
later time to get new messages, a duplicate message is added for each
message that came in with the previous call.

For notmuch at least, that's not a big deal because those messages are
mostly hidden, but it'd still be nice to avoid.  This series makes
that possible with

    (setq piem-mail-injection-skipif-predicate

This might also end up being useful outside of avoiding duplicates for
things like this:

    (setq piem-mail-injection-skipif-predicate
          #'<skip message if From: matches X>)

  [1/3] inject: Abbreviate piem-maildir-directory in message
  [2/3] inject: Support skipping messages
  [3/3] notmuch: Extract "known message?" logic to function

 piem-notmuch.el | 32 +++++++++++++----------
 piem.el         | 67 ++++++++++++++++++++++++++++++++++++-------------
 2 files changed, 68 insertions(+), 31 deletions(-)

base-commit: 846c69cae321442bb2f5cefec7000328943c7560

             reply	other threads:[~2020-08-22 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 19:01 Kyle Meyer [this message]
2020-08-22 19:01 ` [PATCH 1/3] inject: Abbreviate piem-maildir-directory in message Kyle Meyer
2020-08-22 19:01 ` [PATCH 2/3] inject: Support skipping messages Kyle Meyer
2020-08-22 19:01 ` [PATCH 3/3] notmuch: Extract "known message?" logic to function Kyle Meyer

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:

  List information: https://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200822190130.20397-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).