<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/doc/man1, branch 0.30_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-05-08T11:58:46Z</updated>
<entry>
<title>notmuch(1): clarify documentation about --option/value separators</title>
<updated>2020-05-08T11:58:46Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-07T19:26:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2bf1b256f4eeb8c5e08129a2f0976da2569ce'/>
<id>urn:sha1:02a2bf1b256f4eeb8c5e08129a2f0976da2569ce</id>
<content type='text'>
id:CA+Tk8fzRiqxWpd=r8=DRvEewNZXUZgD7MKyRLB1A=R-LxxGEZw@mail.gmail.com
started a thread of discussion that showed that the cli's current
idiosyncrasies around dealing with boolean options were not
understandable.

This attempts to improve the documentation at least (actual changes to
the API might be better, but have not reached consensus).

Note that no one in the discussion thread identified any other
(non-boolean) command-line options that cannot use space as a
separator.  If such an option is identified (or introduced in the
future), it should be added explicitly to this part of the manual.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>Drop deprecated/unused crypto.gpg_path</title>
<updated>2020-02-19T12:17:49Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-02-18T22:42:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=018ad3703ba46ea603854f51f8ff5ae86183cca0'/>
<id>urn:sha1:018ad3703ba46ea603854f51f8ff5ae86183cca0</id>
<content type='text'>
crypto.gpg_path was only used when we built against gmime versions
before 3.0.  Since we now depend on gmime 3.0.3 or later, it is
meaningless.

The removal of the field from the _notmuch_config struct would be an
ABI change if that struct were externally exposed, but it is not, so
it's safe to unilaterally remove it.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>doc: clean up manpage description of "notmuch-config list" output</title>
<updated>2020-01-16T10:38:29Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-01-10T18:58:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=aba7fb375bf4edad5da40134b4e7a390a881792b'/>
<id>urn:sha1:aba7fb375bf4edad5da40134b4e7a390a881792b</id>
<content type='text'>
The escaping in the description of the output of "notmuch-config list"
appears to have been inherited from some previous attempts at
documentation.  It leaked out in the actual generated manpage
documentation, where it looks like this:

       list   Every  configuration  item is printed to stdout, each on a
              separate line of the form:

                 *section*.\ *item*\ =\ *value*

This simplification cleans up the overescaping.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>doc: document user header indexing.</title>
<updated>2019-05-25T10:21:21Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-02-18T13:08:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9dedb23b47961047d75ef08210481018042d0baf'/>
<id>urn:sha1:9dedb23b47961047d75ef08210481018042d0baf</id>
<content type='text'>
It's a bit odd that the primary documentation is in notmuch-config,
but it is consistent with the "query:" prefix.
</content>
</entry>
<entry>
<title>doc: document notmuch new --verbose</title>
<updated>2019-03-31T14:59:46Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2019-03-29T09:48:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1e69bb6f46ae0468dede6d8977f45295a84b7343'/>
<id>urn:sha1:1e69bb6f46ae0468dede6d8977f45295a84b7343</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: fix references to search.exclude_tags</title>
<updated>2019-01-27T12:18:38Z</updated>
<author>
<name>Peter Wang</name>
<email>novalazy@gmail.com</email>
</author>
<published>2019-01-27T06:54:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6784d5bc60f850a93e6101e60b03bf6ab81020cc'/>
<id>urn:sha1:6784d5bc60f850a93e6101e60b03bf6ab81020cc</id>
<content type='text'>
The documentation incorrectly referred to a configuration item
"search.tag_exclude" in some places, instead of "search.exclude_tags".
</content>
</entry>
<entry>
<title>cli: notmuch show support for --include-html with --format=text</title>
<updated>2018-11-24T13:12:30Z</updated>
<author>
<name>Maxime Coste</name>
<email>mawww@kakoune.org</email>
</author>
<published>2018-10-30T23:54:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=baa4185c302a246e632054dc6becb46c0024b99d'/>
<id>urn:sha1:baa4185c302a246e632054dc6becb46c0024b99d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cli: notmuch show support for --body=false with --format=text</title>
<updated>2018-11-24T13:11:42Z</updated>
<author>
<name>Maxime Coste</name>
<email>mawww@kakoune.org</email>
</author>
<published>2018-10-30T23:54:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=37e5bc00aeb9123dd88367b7506a19f74877dfe4'/>
<id>urn:sha1:37e5bc00aeb9123dd88367b7506a19f74877dfe4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: clean up manpages</title>
<updated>2018-06-25T00:59:37Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-06-19T22:36:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fd3c93650d976f630ba0a60341a1a695422e4969'/>
<id>urn:sha1:fd3c93650d976f630ba0a60341a1a695422e4969</id>
<content type='text'>
Many of the manpages didn't treat literal text as literal text.  I've
tried to normalize some of the restructured text to make it a bit more
regular.

several of the synopsis lines are still untouched by this cleanup, but
i'm not sure what the right way to represent those is in .rst,
actually.

In particular find that if i rebuild the manpages, sometimes i end up
with some of the synopsis lines showing – (U+2013 EN DASH) where they
should have -- (2 × U+002D HYPHEN-MINUS) in the generated nroff
output, though i have not tracked down the source of this error yet.
</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>
</feed>
