From: Kim ALLAMANDOLA <kim-nmml@kfx.fr>
To: notmuch@notmuchmail.org
Subject: Re: notcoal, filters not made from (char)coal / initial tagging system
Date: Mon, 12 Nov 2018 14:29:53 +0100 [thread overview]
Message-ID: <874lcmtodq.fsf@kws.xnet.lan> (raw)
In-Reply-To: <e15d7714df62c6115f79012e1e5d5618bdaef4ec@ftmeade.nsa.gov>
Hi,
being a new notmuch user (using it since around an year) I have a small,
obscenely written, badly shaped, mixed language collection of homegrown
scripts to automate my message handling / mail-based workflow.
Most part are zsh wrappers to autotag (autorefile for now is done by
IMAPFilter) and support manual delete/refile messages, a small part in
an initial state is automation in the sense of extracting mime
attachments (via uudeview) like periodic invoices and properly archive,
renaming attachments etc in a personal docs taxonomy so having a more
well-shaped and ready out-of-the box solution is really welcomed!
The only part I do not like too much is the choice of json instead of
something, *for me*, less ugly to write/read, less error-prone and more
flexible like simple plain guile (GNU embeddable, lightweight scheme
dialect).
The re-write of notmuch in Rust, well... it's outside my scope since I
use it as a "final product", I'm in general favourable to ditch "myths"
like C and C++ and Java, ... for more comfortable languages but for me
nor Rust nor Go really fell in that category, IMO the best paths is
rediscover lisp/scheme languages even if I know that in some cases are
harder to use (while far easier in other) however as said before I'm
only a user so I have to thanks all notmuch and notmuch-related devs
for their wonderful works, I'll try Rust port anyway :-)
-- Kim
next prev parent reply other threads:[~2018-11-12 17:08 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 [this message]
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
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=874lcmtodq.fsf@kws.xnet.lan \
--to=kim-nmml@kfx.fr \
--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).