<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch debian/0.27-2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.27-2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.27-2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2018-05-26T23:46:44Z</updated>
<entry>
<title>test: fix hardcoded paths in T050-new.sh</title>
<updated>2018-05-26T23:46:44Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-05-26T23:46:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=46cf1a98f3616f1a503f7b04c0f6980930aedaf2'/>
<id>urn:sha1:46cf1a98f3616f1a503f7b04c0f6980930aedaf2</id>
<content type='text'>
The previous paths will fail almost everywhere.
</content>
</entry>
<entry>
<title>cli/show: enable --decrypt=stash</title>
<updated>2018-05-26T14:43:30Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-05-11T06:57:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=aa605f7e8a4c5e046503d61fdb953721c32f9d3a'/>
<id>urn:sha1:aa605f7e8a4c5e046503d61fdb953721c32f9d3a</id>
<content type='text'>
Add fancy new feature, which makes "notmuch show" capable of actually
indexing messages that it just decrypted.

This enables a workflow where messages can come in in the background
and be indexed using "--decrypt=auto".  But when showing an encrypted
message for the first time, it gets automatically indexed.

This is something of a departure for "notmuch show" -- in particular,
because it requires read/write access to the database.  However, this
might be a common use case -- people get mail delivered and indexed in
the background, but only want access to their secret key to happen
when they're directly interacting with notmuch itself.

In such a scenario, they couldn't search newly-delivered, encrypted
messages, but they could search for them once they've read them.

Documentation of this new feature also uses a table form, similar to
that found in the description of index.decrypt in notmuch-config(1).

A notmuch UI that wants to facilitate this workflow while also
offering an interactive search interface might instead make use of
these additional commands while the user is at the console:

Count received encrypted messages (if &gt; 0, there are some things we
haven't yet tried to index, and therefore can't yet search):

     notmuch count tag:encrypted and \
         not property:index.decryption=success and \
         not property:index.decryption=failure

Reindex those messages:

     notmuch reindex --try-decrypt=true tag:encrypted and \
         not property:index.decryption=success and \
         not property:index.decryption=failure
</content>
</entry>
<entry>
<title>test-lib: add notmuch_show_part for "notmuch show --format=text"</title>
<updated>2018-05-26T14:42:28Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-05-11T06:57:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9d114a855260b3df194691c9bbf904fa08a3f0d0'/>
<id>urn:sha1:9d114a855260b3df194691c9bbf904fa08a3f0d0</id>
<content type='text'>
Thanks to David Bremner for this improved readability!
</content>
</entry>
<entry>
<title>test: use --full-scan in T050-new.sh</title>
<updated>2018-05-22T16:29:59Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-04-29T23:19:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=84b29637261adc3c647e078ad320258b371bd36b'/>
<id>urn:sha1:84b29637261adc3c647e078ad320258b371bd36b</id>
<content type='text'>
Wherever the test relies on directories being scanned, this option
should be used to avoid skipping them due to mtimes on directories
matching the database.
</content>
</entry>
<entry>
<title>test: add tests for notmuch new --full-scan</title>
<updated>2018-05-22T16:29:48Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-04-29T23:19:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d1acff615306a732054b3cc2bec502a419ed861a'/>
<id>urn:sha1:d1acff615306a732054b3cc2bec502a419ed861a</id>
<content type='text'>
Most of these just check that adding the flag does not break existing
functionality. The one test that does check the full-scan
functionality had to be rewritten to output debugging info.
</content>
</entry>
<entry>
<title>build: Allow user to specify ruby executable</title>
<updated>2018-05-11T00:01:06Z</updated>
<author>
<name>Thomas Schneider</name>
<email>qsx@chaotikum.eu</email>
</author>
<published>2018-05-09T12:38:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b2e4778ea4a704e4a86ae41d680a9ec886e66cfa'/>
<id>urn:sha1:b2e4778ea4a704e4a86ae41d680a9ec886e66cfa</id>
<content type='text'>
This way, one can build for a different Ruby than $PATH/ruby
(e. g. different versions, or Ruby in other paths).

Signed-off-by: Thomas Schneider &lt;qsx@chaotikum.eu&gt;
</content>
</entry>
<entry>
<title>lib: add thread subqueries.</title>
<updated>2018-05-07T11:42:53Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-12-26T01:03:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5ad39ebf75eb85263e4b64f21e07ec02194f9573'/>
<id>urn:sha1:5ad39ebf75eb85263e4b64f21e07ec02194f9573</id>
<content type='text'>
This change allows queries of the form

 thread:{from:me} and thread:{from:jian} and not thread:{from:dave}

This is still somewhat brute-force, but it's a big improvement over
both the shell script solution and the previous proposal [1], because it
does not build the whole thread structure just generate a
query. A further potential optimization is to replace the calls to
notmuch with more specialized Xapian code; in particular it's not
likely that reading all of the message metadata is a win here.

[1]: id:20170820213240.20526-1-david@tethera.net
</content>
</entry>
<entry>
<title>T460-emacs-tree: sync $EXPECTED with test name</title>
<updated>2018-05-04T00:03:33Z</updated>
<author>
<name>Florian Klink</name>
<email>flokli@flokli.de</email>
</author>
<published>2018-04-19T08:41:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=140e8fb11814038647ee30d01fec2e1bd1368605'/>
<id>urn:sha1:140e8fb11814038647ee30d01fec2e1bd1368605</id>
<content type='text'>
This syncs the $EXPECTED directory name with the tests filename.

Signed-off-by: Florian Klink &lt;flokli@flokli.de&gt;
</content>
</entry>
<entry>
<title>move more http -&gt; https</title>
<updated>2018-05-03T23:59:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-04-29T08:35:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c20a5eb80520a11cb697a45b0d9553c68e2199c8'/>
<id>urn:sha1:c20a5eb80520a11cb697a45b0d9553c68e2199c8</id>
<content type='text'>
Correct URLs that have crept into the notmuch codebase with http://
when https:// is possible.

As part of this conversion, this changeset also indicates the current
preferred upstream URLs for both gmime and sup.  the new URLs are
https-enabled, the old ones are not.

This also fixes T310-emacs.sh, thanks to Bremner for catching it.
</content>
</entry>
<entry>
<title>test: add known broken test for regexp search of second subject</title>
<updated>2018-05-03T10:44:49Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-12-14T14:32:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4ac23c5978ff963c18a012b6b230b26f9ef98c43'/>
<id>urn:sha1:4ac23c5978ff963c18a012b6b230b26f9ef98c43</id>
<content type='text'>
We expect this to give the same answer as the non-regexp subject
search. It does not because the regexp search relies on the value
slot, which currently contains only one subject.
</content>
</entry>
</feed>
