<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/completion, branch debian/0.40_rc0-2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.40_rc0-2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.40_rc0-2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-11-05T17:18:15Z</updated>
<entry>
<title>cli: add options --offset and --limit to notmuch show</title>
<updated>2022-11-05T17:18:15Z</updated>
<author>
<name>Robin Jarry</name>
<email>robin@jarry.cc</email>
</author>
<published>2022-10-18T19:41:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=793f2980910f612fa33806ef71fa7ee35d093657'/>
<id>urn:sha1:793f2980910f612fa33806ef71fa7ee35d093657</id>
<content type='text'>
notmuch search does not output header values. However, when browsing
through a large email corpus, it can be time saving to be able to
paginate without running notmuch show for each message/thread.

Add --offset and --limit options to notmuch show. This is inspired from
commit 796b629c3b82 ("cli: add options --offset and --limit to notmuch
search").

Update man page, shell completion and add a test case to ensure it works
as expected.

Cc: Tim Culverhouse &lt;tim@timculverhouse.com&gt;
Cc: Tomi Ollila &lt;tomi.ollila@iki.fi&gt;
Signed-off-by: Robin Jarry &lt;robin@jarry.cc&gt;
</content>
</entry>
<entry>
<title>completion: use mail_root for path completion in bash/zsh</title>
<updated>2022-01-03T12:07:38Z</updated>
<author>
<name>Cédric Hannotier</name>
<email>cedric.hannotier@ulb.be</email>
</author>
<published>2021-12-16T17:40:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d99b0d4dc8b9262373e2d0ae158dd8336fc28e41'/>
<id>urn:sha1:d99b0d4dc8b9262373e2d0ae158dd8336fc28e41</id>
<content type='text'>
Since mail store and database directory can be different,
path and folder completions must use the directory given by
database.mail_root, not by database.path.
</content>
</entry>
<entry>
<title>emacs: Use makefile-gmake-mode in Makefile*s</title>
<updated>2020-08-10T00:14:36Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c4541353765dec837c1c2f912b1bf6661827429c'/>
<id>urn:sha1:c4541353765dec837c1c2f912b1bf6661827429c</id>
<content type='text'>
Use `makefile-gmake-mode' instead of `makefile-mode' because the
former also highlights ifdef et al. while the latter does not.

"./Makefile.global" and one "Makefile.local" failed to specify any
major mode at all but doing so is necessary because Emacs does not
automatically figure out that these are Makefiles (of any flavor).
</content>
</entry>
<entry>
<title>completion: more complete completion for zsh.</title>
<updated>2018-10-03T00:04:26Z</updated>
<author>
<name>Vincent Breitmoser</name>
<email>look@my.amazin.horse</email>
</author>
<published>2018-09-18T11:19:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=07eac4af32ab1b955fcf3405dcf14b0f01af8702'/>
<id>urn:sha1:07eac4af32ab1b955fcf3405dcf14b0f01af8702</id>
<content type='text'>
This adds completion files for zsh that cover most of notmuch's cli.

The files in completion/zsh are formatted so that they can be found by
zsh's completion system if put $fpath. They are also registered to the
notmuch-* pattern, so they can be called externally using _dispatch.

Update installation recipe and drop debian/notmuch.examples to avoid
breakage. This means zsh completion is not installed for debian, to be
fixed in a future commit.

Amended by db: use regexp searching for address completion. This seems
to be fast enough to work without a cache.
</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>cli/reply: make --decrypt take a keyword</title>
<updated>2017-12-29T20:45:55Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:40:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=af8255fb7159652a7d4e1fe4f1398302e1746cce'/>
<id>urn:sha1:af8255fb7159652a7d4e1fe4f1398302e1746cce</id>
<content type='text'>
This brings the --decrypt argument to "notmuch reply" into line with
the other --decrypt arguments (in "show", "new", "insert", and
"reindex").  This patch is really just about bringing consistency to
the user interface.

We also use the recommended form in the emacs MUA when replying, and
update test T350 to match.
</content>
</entry>
<entry>
<title>cli/show: make --decrypt take a keyword.</title>
<updated>2017-12-29T20:45:46Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:40:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8ea4a99d74737929f58568505e41c94f65a14743'/>
<id>urn:sha1:8ea4a99d74737929f58568505e41c94f65a14743</id>
<content type='text'>
We also expand tab completion for it, update the emacs bindings, and
update T350, T357, and T450 to match.

Make use of the bool-to-keyword backward-compatibility feature.
</content>
</entry>
<entry>
<title>cli: add support for only printing the addresses in notmuch address</title>
<updated>2017-12-15T01:28:50Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-11-02T18:44:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f3fc97c0008c1d48ccac88c52b5bae61460bfa3f'/>
<id>urn:sha1:f3fc97c0008c1d48ccac88c52b5bae61460bfa3f</id>
<content type='text'>
The notmuch address output is much more useful for scripts with just
the addresses printed. Support this using the --output=address option.
</content>
</entry>
<entry>
<title>cli/help,completion: added pointers to notmuch-properties(7)</title>
<updated>2017-12-11T13:11:19Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-10-26T21:28:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=94dc81a91b2f300d1c583cc10956869d29c645a8'/>
<id>urn:sha1:94dc81a91b2f300d1c583cc10956869d29c645a8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>crypto: add --decrypt=nostash to avoid stashing session keys</title>
<updated>2017-12-08T12:08:47Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-08T06:24:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fccebbaeef1e4b6489425afb13f419543d53d285'/>
<id>urn:sha1:fccebbaeef1e4b6489425afb13f419543d53d285</id>
<content type='text'>
Here's the configuration choice for people who want a cleartext index,
but don't want stashed session keys.

Interestingly, this "nostash" decryption policy is actually the same
policy that should be used by "notmuch show" and "notmuch reply",
since they never modify the index or database when they are invoked
with --decrypt.

We take advantage of this parallel to tune the behavior of those
programs so that we're not requesting session keys from GnuPG during
"show" and "reply" that we would then otherwise just throw away.
</content>
</entry>
</feed>
