<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs/notmuch-query.el, branch 0.7</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.7</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.7'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2011-05-27T23:22:00Z</updated>
<entry>
<title>emacs: Add support for PGP/MIME verification/decryption</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-26T01:01:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=45fe3547458e0c403f7501bad89860afe2fa534a'/>
<id>urn:sha1:45fe3547458e0c403f7501bad89860afe2fa534a</id>
<content type='text'>
A new emacs configuration variable "notmuch-crypto-process-mime"
controls the processing of PGP/MIME signatures and encrypted parts.
When this is set true, notmuch-query will use the notmuch show
--decrypt flag to decrypt encrypted messages and/or calculate the
sigstatus of signed messages.  If sigstatus is available, notmuch-show
will place a specially color-coded header at the begining of the
signed message.

Also included is the ability to switch decryption/verification on/off
on the fly, which is bound to M-RET in notmuch-search-mode.
</content>
</entry>
<entry>
<title>emacs: send notmuch-query stderr to /dev/null</title>
<updated>2011-01-27T04:44:05Z</updated>
<author>
<name>Jameson Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-01-26T20:57:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=15d8928f4133eb28f7823b0f4d4c5edc6471131c'/>
<id>urn:sha1:15d8928f4133eb28f7823b0f4d4c5edc6471131c</id>
<content type='text'>
The call-process to notmuch in notmuch-query.el was previously sending
stderr into the output buffer.  This means that if there is any stderr
the JSON parsing breaks.  Unfortunately call-process does not support
sending stderr to a separate buffer or to the minibuffer [0], but it
does support sending it to /dev/null.  So we do that here instead.

[0] a bug was filed against emacs (#7842)
</content>
</entry>
<entry>
<title>emacs: Fix to eliminate warning in notmuch-query-map-aux</title>
<updated>2010-10-28T00:54:38Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-28T00:54:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4ddb5ab4dd42208ba24989f188bdd06ab7865b5e'/>
<id>urn:sha1:4ddb5ab4dd42208ba24989f188bdd06ab7865b5e</id>
<content type='text'>
This is one of those cases where the warning looks absolutely correct,
(complaining about a free variable), but I'm left wondering how the
original code could have worked at all.

From what I can tell, this code wasn't actually being called by any
of the current code in notmuch.
</content>
</entry>
<entry>
<title>notmuch-query.el: new file to support access to the notmuch database.</title>
<updated>2010-04-05T18:08:45Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@unb.ca</email>
</author>
<published>2010-04-05T16:46:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c2f3710a786dc8d610ccd8138ccfe5089686bec2'/>
<id>urn:sha1:c2f3710a786dc8d610ccd8138ccfe5089686bec2</id>
<content type='text'>
Initially this file provides one main function
notmuch-query-get-threads, which takes a set of search terms, and
returns a parsed set of matching threads as a lisp data structure.

A set of notmuch-query-map-* functions are provided to help map
functions over the data structure.

The function notmuch-query-get-message-ids uses this machinery to get
the set of message-ids matching a query.

Edited-by: Carl Worth &lt;cworth@cworth.org&gt;: Change comment syntax,
(";;" rather than ";" to make emacs-lisp mode happy), and eliminate
some excess whitespace, as suggested by David Edmonson.
</content>
</entry>
</feed>
