<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch 0.24</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.24</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.24'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-03-05T01:21:11Z</updated>
<entry>
<title>test: shrink T590-thread-breakage test decription to one line</title>
<updated>2017-03-05T01:21:11Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-26T17:36:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=85df8b3915159fa94b7c1c32cb54eda8bd92e0e0'/>
<id>urn:sha1:85df8b3915159fa94b7c1c32cb54eda8bd92e0e0</id>
<content type='text'>
The test description is used for log output, I think the intention is
to keep it as a one-liner. Leave the rest of the long description as a
comment.
</content>
</entry>
<entry>
<title>Test: emacs: test for folding long headers.</title>
<updated>2017-03-05T01:15:55Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2017-03-04T20:42:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a8f91b74e7a52306919452e3593d2a8a1e529bd1'/>
<id>urn:sha1:a8f91b74e7a52306919452e3593d2a8a1e529bd1</id>
<content type='text'>
Headers of more than 998 characters should be folded when sending.
However, until recently, emacs did not do this.

This adds a (known broken) test for this when sending messages in
emacs. We will backport the fix to notmuch-emacs in the next
changeset.
</content>
</entry>
<entry>
<title>lib: query make exclude handling non-destructive</title>
<updated>2017-03-05T00:47:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-25T16:09:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dfacfe14f337b6603ba0784e4a395489923fd6dd'/>
<id>urn:sha1:dfacfe14f337b6603ba0784e4a395489923fd6dd</id>
<content type='text'>
We filter added exclude at add time, rather than modifying the query by
count search. As noted in the comments, there are several ignored
conditions here.
</content>
</entry>
<entry>
<title>lib: centralize query parsing, store results.</title>
<updated>2017-03-05T00:47:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-25T16:09:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e209b7187365b9f5a356b21f3d11dd2f41fd5a1c'/>
<id>urn:sha1:e209b7187365b9f5a356b21f3d11dd2f41fd5a1c</id>
<content type='text'>
The main goal is to prepare the way for non-destructive (or at least
less destructive) exclude tag handling. It does this by having a
pre-parsed query available for further processing. This also allows us
to provide slightly more precise error messages.
</content>
</entry>
<entry>
<title>lib: add mid: as a synonym for id:</title>
<updated>2017-03-03T21:46:48Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-27T02:34:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6cb1c617a70466c4d8acc67cb70254e5b8385f88'/>
<id>urn:sha1:6cb1c617a70466c4d8acc67cb70254e5b8385f88</id>
<content type='text'>
mid: is the url scheme suggested by URL 2392. We also plan to
introduce more flexible searches for mid: than are possible with
id: (in order not to break assumptions about the special behaviour of
id:, e.g. identifying at most one message).
</content>
</entry>
<entry>
<title>lib: regexp matching in 'subject' and 'from'</title>
<updated>2017-03-03T21:46:48Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-27T02:34:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=55524bb063c95ae51a1762eb0b1aacce6ca49223'/>
<id>urn:sha1:55524bb063c95ae51a1762eb0b1aacce6ca49223</id>
<content type='text'>
the idea is that you can run

% notmuch search subject:/&lt;your-favourite-regexp&gt;/
% notmuch search from:/&lt;your-favourite-regexp&gt;/

or

% notmuch search subject:"your usual phrase search"
% notmuch search from:"usual phrase search"

This feature is only available with recent Xapian, specifically
support for field processors is needed.

It should work with bindings, since it extends the query parser.

This is easy to extend for other value slots, but currently the only
value slots are date, message_id, from, subject, and last_mod. Date is
already searchable;  message_id is left for a followup commit.

This was originally written by Austin Clements, and ported to Xapian
field processors (from Austin's custom query parser) by yours truly.
</content>
</entry>
<entry>
<title>Merge branch 'release'</title>
<updated>2017-03-01T01:21:07Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-03-01T01:21:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=508b5c20fa38b17fa527af075857061f4ed81e2a'/>
<id>urn:sha1:508b5c20fa38b17fa527af075857061f4ed81e2a</id>
<content type='text'>
Second gnugpg test suite fix
</content>
</entry>
<entry>
<title>cli/show: add content-disposition to structured output message parts</title>
<updated>2017-02-28T12:03:00Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-26T18:33:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ea20a932f1b8bc849db5ed35c1f355990f186146'/>
<id>urn:sha1:ea20a932f1b8bc849db5ed35c1f355990f186146</id>
<content type='text'>
Help the clients decide how to display parts.

Test updates by Mark Walters &lt;markwalters1009@gmail.com&gt;.
One more test fix by db
</content>
</entry>
<entry>
<title>test: move GNUPGHOME to TEST_TMPDIR</title>
<updated>2017-02-28T00:01:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-27T23:53:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1044775fc003914ee63b53254b7ca8700983a6e7'/>
<id>urn:sha1:1044775fc003914ee63b53254b7ca8700983a6e7</id>
<content type='text'>
We already use this directory for dtach sockets, so it makes sense to
put gnupg sockets there as well. There doesn't seem to be a clean way
to put a fully functional socket in a different location than
GNUPGHOME.
</content>
</entry>
<entry>
<title>Revert "test: use gpgconf --create-socketdir if available"</title>
<updated>2017-02-27T22:26:47Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-27T22:26:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5a42bb96c1ad4fcbcbf3dc882ba814c06e657f98'/>
<id>urn:sha1:5a42bb96c1ad4fcbcbf3dc882ba814c06e657f98</id>
<content type='text'>
This reverts commit e7b88e8b0a93ca83d807edc00e0c97af54c5b5f1.

It turns out that this does not work well in environments without a
running systemd (or some other provider of /run/user)
</content>
</entry>
</feed>
