misc material i use with notmuch mail indexer
my personal “extensions” around notmuch mail indexer that are too specific to be added to http://notmuchmail.org/ wiki, with additional scripts that aren't feasible to be stored to the wiki.
address completion:
nottoomuch-addresses | selection-menu
mail sending:
nottoomuch-emacs-mailto | nottoomuch-xdg-email
mail delivery:
remote access:
building:
- nottoomuch-addresses
- the address completion provider i use to get list of email addresses from where email addresses is selected when sending emails.
- selection-menu
- the address completion tool i use to complete email addresses when sending emails.
- nottoomuch-emacs-mailto
- send mail from e.g. following mailto: link in web browsers, using notmuch emacs client.
- nottoomuch-xdg-email
- wrap
xdg-emailwith this (by putting this asxdg-emailin$PATHbefore the system one) so that nottoomuch-emacs-mailto is used as the mailer.
- startfetchmail
- the fetchmail startup script i use to get it configured as required and to see that startup succeeded (failures due to incorrect password etc).
- md5mda
the mail delivery agent i uset to get mails delivered from fetchmail to target directories. mails are finally delivered to subdirs whose first 2 characters are 2 first hexdigits of the md5sum of the file contents and the file name is rest 30 hexdigits of the file md5sum.
startfetchmail provides an example how md5mda is used.
- nottoomuch-remote
- access notmuch on remote machine using ssh without passwordless login requirement.
- make-one-notmuch-el
- i like to have the notmuch emacs byte-compiled file available as a one
file which is easy to carry along. this script combines all notmuch .el
files together (with minor adjustments) in suitable order for
byte-compilation as one file to succeed. the final
one-notmuch.elcis somewhat smaller than all notmuch.elcfiles separately and may even load a bit faster. i've been using this for quite a long time and have not had problems -- but ymmv with your different setup in case trying this option.
some code that has not reached suitable maturity state (I am using to distribute changes to many dev machines) or is lacking reasonable ux/documentation, is located in wip/ subdictory.
anything can be sent digitally to the email address below, or the ways any particular code repository interfaces provide (in case i receive email notication). thanks for all contributions i've received so far.
how contributions appear to the repository is another issue. in any case proper attribution is given in all cases (preferably as commit author but sometimes in other ways...).
too ät iki dot fi