As its name implies, notmuch isn't really doing that much (which is part of its appeal to many of us). However, it enables a whole ecosystem of surrounding scripts to work in conjunction with notmuch
* [notmuchsync](http://spaetz.github.com/notmuchsync/)
- notmuchsync is a python tool that allows
-* [cnotmuch](http://pypi.python/pypi/cnotmuch) python bindings for the notmuch shared library. Extensive API documentation available.
+ notmuchsync is a python tool that allows synchronization of maildir flags to/from notmuch tags.
+* [cnotmuch](http://pypi.python.org/pypi/cnotmuch) python bindings for the notmuch shared library. Extensive API documentation available.
+* [addrlookup](http://github.com/spaetz/vala-notmuch) vala spplication that can be used for interactive email address completion.
* gitmuch?
* ...
-----
<h2 id="advanced_tips">Advanced tips and tweaks</h2>
-* <span id="fcc">How to do FCC/BCC...</span>
+* <span id="fcc">**How to do FCC/BCC...**</span>
Any notmuch reply will automatically include your primary email
address in a BCC so that any messages you send will (eventually) end
- up in your mail store as well.
-
- But this doesn't do anything for messages that you compose that are
- not replies. So we need to get sane message-mode FCC figured
- out. Some investigation is still needed here.
+ up in your mail store as well. But this doesn't do anything for
+ messages that you compose that are not replies.
+
+ Another method is described in [this
+ mail](http://mid.gmane.org/878wbj4nfq.fsf@servo.finestructure.net)
+ (id:878wbj4nfq.fsf@servo.finestructure.net). It involves a trivial
+ python script (which should be rewritten in lisp and integrated into
+ the notmuch frontend, really, but is not difficult to setup.
+
+ This is the code I needed in my .emacs file to make it work with
+ the python wrapper that I called mddeliver.py:
+
+ ;; fcc handler
+ (defun maildir-deliver-region(destdir)
+ (shell-command-on-region
+ (point-min) (point-max)
+ (concat "/usr/local/bin/mddeliver.py -c -s -d " destdir)))
+ (setq message-fcc-handler-function 'maildir-deliver-region)
+ (defun my-message-header-setup ()
+ (message-add-header "Fcc: ~/mail/INBOX.Sent"))
+ (add-hook 'message-send-hook 'my-message-header-setup)
* <span id="customize_notmuch_folder">How to customize notmuch-folders</span>
the rest will go to the default account.
* <span id="sync_maildir_flags">how to sync notmuch tags and maildir
- flags]</span>
+ flags</span>
There is no built-in support for sunchronizing your notmuch tags
with your imap maildir flags (seen, replied, trashed, etc). However
*id:1267450136-31749-1-git-send-email-Sebastian@SSpaeth.de* and can
be viewed as a [source diff in this git
repository](http://github.com/spaetz/notmuch-all-feature/commit/df3b087cefb85e9d16fd17540e348bcb854dd7ee).
+
+* <span id="address_completion">**how to get email address completion**</span>
+ There are 2 solutions. Use "bbdb" which allows you to maintain a mail database and gives you mail address completion with the tab key.
+
+ Alternatively, you use the notmuch database as a mail address book itself. This is how you compile the (3rd party) tool "addrlookup" to give you address completion:
+
+ - you need the addrlookup binary, first of all. Grab http://github.com/spaetz/vala-notmuch/raw/static-sources/src/addrlookup.c and build it with *cc -o addrlookup addrlookup.c `pkg-config --cflags --libs gobject-2.0` -lnotmuch*. That should give you the binary that you can test already.
+
+ - EUDC is integrated into emacs and can be used for tab completion
+ of email addresses. The code I use is here
+ http://gist.github.com/359425. It was announce in [this
+ mail](http://mid.gmane.org/87fx3uflkx.fsf@jhu.edu)
+ (id:87fx3uflkx.fsf@jhu.edu) which contains links to the git
+ repositories which contain the files.
\ No newline at end of file
projects / obsolete / notmuch-wiki / blobdiff