<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs/notmuch-lib.el, branch 0.16</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.16</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.16'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-07-20T12:13:48Z</updated>
<entry>
<title>emacs: dropped rest of now-unused JSON functionality</title>
<updated>2013-07-20T12:13:48Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2013-07-06T12:49:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2bd374c91efd6ed0c42fb6ff5b4b969ec0e16cee'/>
<id>urn:sha1:2bd374c91efd6ed0c42fb6ff5b4b969ec0e16cee</id>
<content type='text'>
Notmuch cli provides all structured data previously provided
in json format now in s-expression format, rendering all current
json functionality obsolete.
</content>
</entry>
<entry>
<title>emacs: Remove `notmuch-call-notmuch-json'</title>
<updated>2013-06-25T05:57:28Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-06-23T23:43:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8222af3ecc7e0c33efc834acbae82df1356abe8d'/>
<id>urn:sha1:8222af3ecc7e0c33efc834acbae82df1356abe8d</id>
<content type='text'>
This function is no longer used.
</content>
</entry>
<entry>
<title>emacs: Introduce `notmuch-call-notmuch-sexp'</title>
<updated>2013-06-25T05:57:02Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-06-23T23:43:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2626d815733b5ee04080bc81c75311d812b7c6f5'/>
<id>urn:sha1:2626d815733b5ee04080bc81c75311d812b7c6f5</id>
<content type='text'>
This is just like `notmuch-call-notmuch-json', but parses S-expression
output.  Note that, also like `notmuch-call-notmuch-json', this
doesn't consider trailing data to be an error, which may or may not be
what we want in the long run.
</content>
</entry>
<entry>
<title>emacs: update search sort order help to match code</title>
<updated>2013-06-25T05:51:37Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-06-03T17:56:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c1a42652a173a4bb70ab72388e6ad150d19a2b06'/>
<id>urn:sha1:c1a42652a173a4bb70ab72388e6ad150d19a2b06</id>
<content type='text'>
</content>
</entry>
<entry>
<title>emacs: Don't report CLI signals sent by Emacs as errors</title>
<updated>2013-06-12T14:53:15Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-06-09T04:45:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=634914064bdfa4acb5b489dc03bd4ff5dcda3170'/>
<id>urn:sha1:634914064bdfa4acb5b489dc03bd4ff5dcda3170</id>
<content type='text'>
Previously, when the user killed the search buffer before the CLI
search process had completed, we would report the signal sent by Emacs
to kill the CLI to the user as an error.  Fix this by only reporting
error exits if the process buffer is still live.  We still report
stderr output regardless in case stderr output was relevant to why the
user killed the search buffer (such as a wrapper script being stuck).
</content>
</entry>
<entry>
<title>emacs: Utilities to manage asynchronous notmuch processes</title>
<updated>2013-06-01T11:53:36Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-06-01T00:40:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a13b388243247a423a8c8476e35a4ebe6c9bde5b'/>
<id>urn:sha1:a13b388243247a423a8c8476e35a4ebe6c9bde5b</id>
<content type='text'>
This provides a new notmuch-lib utility to start an asynchronous
notmuch process that handles redirecting of stderr and checking of the
exit status.  This is similar to `notmuch-call-notmuch-json', but for
asynchronous processes (and it leaves output processing to the
caller).
</content>
</entry>
<entry>
<title>emacs: Record part p-list in a text property</title>
<updated>2013-06-01T01:00:52Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-05-30T01:13:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=04725cfbe5a8905651b3f6a4dcf1f3dce9a085e1'/>
<id>urn:sha1:04725cfbe5a8905651b3f6a4dcf1f3dce9a085e1</id>
<content type='text'>
This is similar to what we already do with the message p-list, though
we apply the part's text property to the whole part's text, in
contrast with the message p-list, which is (rather obscurely) only
applied to the first character.
</content>
</entry>
<entry>
<title>emacs: Fix trimming regexp in notmuch-check-exit-status</title>
<updated>2013-05-27T21:19:03Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2013-05-17T20:14:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e7ade21d56b43dafc6dbd517a1b72fcf9d62b238'/>
<id>urn:sha1:e7ade21d56b43dafc6dbd517a1b72fcf9d62b238</id>
<content type='text'>
For such a simple regexp, this was broken in a very complicated way.

The intent was to strip the newline (and potentially other whitespace)
off the end of the error string so there wasn't an extra newline in
the error signal.  However, the regexp was deeply dependent on the
active syntax table and the subtleties of $.  We didn't notice this
because all notmuch major modes put ?\n in the whitespace class, which
makes this behaved as intended: the "\\s " matches all newlines, but
by matching the newline character, causes the $ *not* to match
*except* where it matched the empty string at the very end of the
string, which was not followed by a newline.

However, if the syntax table declares ?\n to be non-whitespace
(lisp-mode declares it as endcomment, and is likely to be the mode
you're in when testing functions), then this regexp behaves completely
differently, matching trailing spaces at the end of every line within
the string.

The solution is to say what we mean for whitespace *and* to switch
from $ to \', which matches only the end of the string, rather than
the end of each line.  Both are necessary or this will strip away
interior newlines, which is not what we want.
</content>
</entry>
<entry>
<title>emacs: removed code attempting to support emaces prior to version 23</title>
<updated>2013-05-14T00:08:10Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2013-03-31T20:04:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ab30a846a49f576e1bfcd73f2ec41def474a6d96'/>
<id>urn:sha1:ab30a846a49f576e1bfcd73f2ec41def474a6d96</id>
<content type='text'>
The support for emacs version 22 has not worked at least since
September 2011 when I attempted to use it. I expanded the support in
id:yf6ippgtbn0.fsf@taco2.nixu.fi but that was not enough and then I
found it easier to switch to emacs 23.
In case one wants to resurrect emacs 22 (or earlier!) support, pick
the changes from the patch email referenced above.
</content>
</entry>
<entry>
<title>emacs: introduce notmuch-command-to-string, replace use of shell-command-to-string</title>
<updated>2013-04-01T11:58:20Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2013-03-08T13:04:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=abd4d6b92e488109a155fdee27285e6df485c583'/>
<id>urn:sha1:abd4d6b92e488109a155fdee27285e6df485c583</id>
<content type='text'>
This has two benefits: unified error handling, and avoiding tramp's
hooking into shell-command-string.

This seems to be a fix for id:874nguxbvq.fsf@tu-dortmund.de
</content>
</entry>
</feed>
