unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Kim ALLAMANDOLA <kim-nmml@kfx.fr>
To: eaon <eaon@mit.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: notcoal, filters not made from (char)coal / initial tagging system
Date: Mon, 12 Nov 2018 20:20:27 +0100	[thread overview]
Message-ID: <87tvkmrtl0.fsf@kws.xnet.lan> (raw)
In-Reply-To: <e56b160e22d4bc1247662291fc36bd8d5c67ac19@ftmeade.nsa.gov>

Hi,
> There's still a couple features missing to have it be as useful as I'd
> like it to be, but it's a start. I'm certainly open to feedback!
For me it's already really nice, essentially overlap some afew features
in a more flexible/extendable manner. My personal automation add mostly
physical message manipulation that can be generalized only to a certain
extent: for instance I have a script that look for mail from my mobile
carrier invoices and automatically extract attached pdf to a specific
taxonomy with a name generated from the invoice number and month
pdfgrep-ed from the pdf itself, same for home ISP, another that look for
"invoice notification" by EDF (home electricity provider) that do not
offer invoices sent as attachments and so add a reminder to manually
download them from EDF's portal in my agenda plus adding "periodic"
self-reading consumption communication schedule/deadline, they also take
care of archiving (mark unread) messages, delete some messages after a
certain amount of time, "snooze" others (mark read upon arrival and at a
certain point in time mark unread again), forge&send new message as a
poor man's agenda notification when I'm not on my desktop (like on
mobile)... I'll plan to add a cross-check from invoices to bank movements
(ledger) to send a remainder if after a certain amount of time an
invoice does not appear to be paid from my bank etc.

Many of those function have some common points and can be cleaned up,
unified in a single language (actually are a mix of zsh scripts, hy
scripts, python scripts, horribly interconnect in "chain-calls") and
inserted in a single library to create a generic tool flexible enough
to be useful for others but they are essentially a sort of chaotic,
primitive PIM suite around an email-centric workflow, the opposite
of notmuch philosophy I suspect. Also many functionality are actually
crude wrappers around other tools that can't be cleanly integrated in
a new one (like IMAPFilter, alot, uudeview, pdfgrep, pdftotext, ledger,
...) so it's more than a simple cleanup and translation...

>> The re-write of notmuch in Rust […]
> Ah, misunderstanding there, maybe. notmuch-rs is not a rewrite or
> port, it's just an interface/bindings for libnotmuch.
Ops... Honestly I look only at notcoal page ignoring the rest leaving
a remainder for next weekend to give a real try :-(

-- Kim

      reply	other threads:[~2018-11-12 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  0:14 notcoal, filters not made from (char)coal / initial tagging system eaon
2018-11-12 13:29 ` Kim ALLAMANDOLA
2018-11-12 17:59   ` David Bremner
2018-11-12 18:21     ` Kim ALLAMANDOLA
2018-11-12 18:04   ` eaon
2018-11-12 19:20     ` Kim ALLAMANDOLA [this message]

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

  List information: https://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87tvkmrtl0.fsf@kws.xnet.lan \
    --to=kim-nmml@kfx.fr \
    --cc=eaon@mit.edu \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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