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 _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch