From: ccx@te2000.cz
Date: Fri, 24 Jun 2011 13:28:21 +0200
To: notmuch@notmuchmail.org
Subject: Notmuch scripts
Message-ID: <20110624112820.GA26201@dorje.inet.te2000>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: list


--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello list!

As some of you know I have written several scripts that aid using
notmuch, including an alternative to the notmuch-mutt perl script.

Since Carl Worth consented to include them into official distribution
I am now cleaning them up, writing docs and extending it so it covers
all features notmuch-mutt currently has.

They can currently be obtained by:
	bzr branch http://webprojekty.cz/ccx/bzr/zmuch
Or you can browse the code at:
	http://webprojekty.cz/ccx/loggerhead/zmuch/files

During the process of polishing the scripts I thought about few things
that may be interesting to other people integrating notmuch, so let me
hear your opinions. :-)

$NOTMUCH and proxies:
There are applications (whether full-blown interfaces or simple scripts)
that use notmuch. There are scrips that work as proxies to actual
notmuch, eg. by invoking ssh to a machine where the mails are, or
processing the argument list and expanding saved searches. Therefore it
would be very practical if the path to actual executable would be
configurable. Thus I propose:

  * Every application that does not act as a proxy should use
    environment variable NOTMUCH to find the actual notmuch executable.
	If not defined or empty, just execute 'notmuch' as usual.

  * Every application that acts as a proxy should ignore the NOTMUCH
	variable, instead it should be configurable in other way
	(configuration file or something easily changeable). This way
	chaining of proxies will be possible.

Configuration and temporary files:
I like XDG specification. I think it's bit unnecessary to have to have
config files that belong only to few scripts littered all around my
homedir. Also I think it's reasonable that user would be able to specify
where to put the temporary files. That said atm I have ~/.zmuch as the
only config file, as it felt bit weird to create new directory for just
one file. But as I'm preparing the scripts I see more and more things
that are specific to my setup and I would like them to be configurable.
These are:

  * Spam filter. Do you guys use any? What does it's interface look like?
    I currently use bsfilter which I've found does it's job pretty well.

  * Colors. I use bright fg on dark bg, but I understand somebody won't
    be happy with this choice.

  * New message processing. Currently I check for spam and I mute
    selected threads. I can see this can be made quite configurable.
	Maybe create procmail equivalent for notmuch? :-)

Thanks for notmuch! I look forward to your responses.
	Jan Pobrislo (ccxCZ@freenode)

--Nq2Wo0NMKNjxTN9z
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk4EdNQACgkQq2Q0xnrW+pm6cwCeMV5l8Jq2BoJ8u1vcz2JTHfPb
GGsAoJeL5e/vmgQ1WKlTNIeFTRHD1y/w
=j+TT
-----END PGP SIGNATURE-----

--Nq2Wo0NMKNjxTN9z--