<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/doc, branch debian/0.23.7-2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.23.7-2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.23.7-2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-01-08T12:35:17Z</updated>
<entry>
<title>docs: add 2017 to copyright years</title>
<updated>2017-01-08T12:35:17Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-01-08T12:35:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=44520bb6add5e39e12de689a168007d3d2c7c734'/>
<id>urn:sha1:44520bb6add5e39e12de689a168007d3d2c7c734</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cli/insert: document the use of EX_TEMPFAIL</title>
<updated>2016-12-15T11:21:02Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-12-07T11:27:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3d312e2577820f7c14df24be305da715d4ea74ee'/>
<id>urn:sha1:3d312e2577820f7c14df24be305da715d4ea74ee</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cli/new: document new exit code</title>
<updated>2016-11-26T02:44:05Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-26T02:40:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0ca79007275ef6430d7f791b1161e39827139c87'/>
<id>urn:sha1:0ca79007275ef6430d7f791b1161e39827139c87</id>
<content type='text'>
It seems important to give the numeric return code for people writing
scripts. Hopefully deviations from this convention are rare.
</content>
</entry>
<entry>
<title>add property: query prefix to search for specific properties</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-07-08T09:15:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=693ca8d8a80438ce1e361e7e6d22288f52a11c55'/>
<id>urn:sha1:693ca8d8a80438ce1e361e7e6d22288f52a11c55</id>
<content type='text'>
We want to be able to query the properties directly, like:

   notmuch count property:foo=bar

which should return a count of messages where the property with key
"foo" has value equal to "bar".
</content>
</entry>
<entry>
<title>cli: optionally restore message properties from dump file</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=651da30c0941081cf730930fc1a7cac34954ca0e'/>
<id>urn:sha1:651da30c0941081cf730930fc1a7cac34954ca0e</id>
<content type='text'>
This somewhat mimics the config line parsing, except there can be
arbitrarily many key value pairs, so one more level of looping is
required.
</content>
</entry>
<entry>
<title>CLI: add properties to dump output</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b7345d277ec5f562000c0e740e6515c2a84f9c76'/>
<id>urn:sha1:b7345d277ec5f562000c0e740e6515c2a84f9c76</id>
<content type='text'>
Part of providing extensibility via properties is to make sure that user
data is not lost. Thus we need to be able to dump and restore
properties.
</content>
</entry>
<entry>
<title>clean up spelling</title>
<updated>2016-09-12T11:16:35Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-09-12T02:23:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=89c8d279480aa618bed5ef074f9166dbf818e6eb'/>
<id>urn:sha1:89c8d279480aa618bed5ef074f9166dbf818e6eb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: update cross references for notmuch.1</title>
<updated>2016-08-23T23:53:52Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-29T19:39:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3ba1b938b56857dc18e4d2b7233b8aba5cad7820'/>
<id>urn:sha1:3ba1b938b56857dc18e4d2b7233b8aba5cad7820</id>
<content type='text'>
In particular add notmuch-compact(1) (Debian bug #825884)
</content>
</entry>
<entry>
<title>doc/notmuch-emacs.rst: update notmuch-hello buffer help text</title>
<updated>2016-06-11T16:02:35Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-06-05T20:38:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6a49e8a51e0591d92ae187af80cf1bedfdd8e09b'/>
<id>urn:sha1:6a49e8a51e0591d92ae187af80cf1bedfdd8e09b</id>
<content type='text'>
To look the same as commit b8a136187a3b changed it in emacs MUA code.
</content>
</entry>
<entry>
<title>doc: clean up boolean vs. probabilistic prefixes</title>
<updated>2016-06-07T11:00:40Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-06-02T16:01:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d080b4100aedbb93a4a4b43f6d07fa2daba101d3'/>
<id>urn:sha1:d080b4100aedbb93a4a4b43f6d07fa2daba101d3</id>
<content type='text'>
sphinx-build emits a minor warning:

[...]doc/man7/notmuch-search-terms.rst:223: WARNING: Block quote ends without a blank line; unexpected unindent.

And the tabular representation of boolean or probabilistic prefixes
currently renders like this when i view it in man:

       ┌───────────────────────────┬────────────────────────────┐
       │Boolean                    │ Probabilistic              │
       └───────────────────────────┴────────────────────────────┘

       │          tag: id:         │           from: to:        │
       │                           │                            │
       │       thread:     folder: │        subject:    attach‐ │
       │       path:               │        ment: mimetype:     │
       └───────────────────────────┴────────────────────────────┘

This isn't just ugly: it's confusing, because it seems to imply that
some of the prefixes in the left-hand column are somehow related to
specific other prefixes in the right-hand column.

The Definition List representation introduced by this patch should be
simpler for readers to understand, and doesn't have the warning.
</content>
</entry>
</feed>
