<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-reply.c, branch feature/git-remote</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=feature%2Fgit-remote</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=feature%2Fgit-remote'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-07-30T11:45:15Z</updated>
<entry>
<title>CLI/reply: support --duplicate argument</title>
<updated>2022-07-30T11:45:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-01T21:45:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=24decfc1dd294b7546da53890f1c4d16105cc8d6'/>
<id>urn:sha1:24decfc1dd294b7546da53890f1c4d16105cc8d6</id>
<content type='text'>
We want the reply used to match that shown e.g. in the emacs
interface. As a first step provide that functionality on the command
line.

Schema does not need updating as the duplicate key was already
present (with a constant value of 1).
</content>
</entry>
<entry>
<title>CLI/show: support --duplicate for structured output</title>
<updated>2022-07-30T11:41:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-01T21:45:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4612f3eb3dbf16bf98ccbadef77d7a6f6361e692'/>
<id>urn:sha1:4612f3eb3dbf16bf98ccbadef77d7a6f6361e692</id>
<content type='text'>
This introduces a new mandatory key for message structures, namely
"duplicate". Per convention in devel/schemata this does _not_ increase
the format version. This means that clients are responsible for
checking that it exists, and not crashing if it does not.

The main functional change is teaching mime_node_open to understand a
'duplicate' argument.

Support for --duplicate in notmuch-reply would make sense, but we
defer it to a later commit.
</content>
</entry>
<entry>
<title>CLI/{count, dump, reindex, reply, show}: enable sexp queries</title>
<updated>2021-09-05T00:07:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-08-24T15:17:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2944d5913319056dfec5c23065932fd1c87a96f6'/>
<id>urn:sha1:2944d5913319056dfec5c23065932fd1c87a96f6</id>
<content type='text'>
The change in each case is to call notmuch_query_create_with_syntax,
relying on the already inherited shared options.  As a bonus we get
improved error handling from the new query creation API.

The remaining subcommand is 'tag', which is a bit trickier.
</content>
</entry>
<entry>
<title>CLI: make variable n_requested_db_uuid file scope.</title>
<updated>2021-09-05T00:07:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-08-24T15:17:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d447b694b498c3e18a22f1eb15139a798c6aab26'/>
<id>urn:sha1:d447b694b498c3e18a22f1eb15139a798c6aab26</id>
<content type='text'>
It turns out that now that we pass an open database into the
subcommands, it is easy to check any requested uuid against the
database at the same time as we process the other shared
arguments. This results in overall less boilerplate code, as well as
making a CLI scope function and variable file scope in notmuch.c.
</content>
</entry>
<entry>
<title>lib: consider all instances of Delivered-To header</title>
<updated>2021-08-30T01:10:08Z</updated>
<author>
<name>Hannu Hartikainen</name>
<email>hannu@hrtk.in</email>
</author>
<published>2021-07-02T09:13:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=717e3dcdc3e55d72c8e4a1948708c34170dbf926'/>
<id>urn:sha1:717e3dcdc3e55d72c8e4a1948708c34170dbf926</id>
<content type='text'>
When using notmuch-reply and guessing the From: address from
Delivered-To headers, I had the wrong address chosen today. This was
because the messages from the notmuch list contain these headers in this
order:

Delivered-To: hannu.hartikainen@gmail.com
...
Delivered-To: hannu@hrtk.in

In my .notmuch-config I have the following configuration:

primary_email=hannu@hrtk.in
other_email=hannu.hartikainen@gmail.com;...

Before this change, notmuch-reply would guess From: @gmail.com because
that is the first Delivered-To header present. After the change, the
primary address is chosen as I would expect.
</content>
</entry>
<entry>
<title>CLI: drop notmuch_config_t from subcommand interface.</title>
<updated>2021-04-07T00:32:36Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-02-27T14:07:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1c747a501c0ed7df5eaa2b994b9ad11d8981c62c'/>
<id>urn:sha1:1c747a501c0ed7df5eaa2b994b9ad11d8981c62c</id>
<content type='text'>
At this point it is unused in all subcommands.
</content>
</entry>
<entry>
<title>cli: run uncrustify</title>
<updated>2021-03-13T12:45:34Z</updated>
<author>
<name>uncrustify</name>
<email>david@tethera.net</email>
</author>
<published>2021-03-13T12:45:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=eef21c284742fa5ae14d7d352acc3a4dc98821ce'/>
<id>urn:sha1:eef21c284742fa5ae14d7d352acc3a4dc98821ce</id>
<content type='text'>
This is the result of running

     $ uncrustify --replace --config devel/uncrustify.cfg *.c *.h

in the top level source directory

Line breaks were then adjusted manually to keep argc and argv
together.
</content>
</entry>
<entry>
<title>CLI/reply: convert to new config framework</title>
<updated>2021-02-06T23:21:23Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-11-08T01:58:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8588719eb1bb14367464214f304b6f93452124c7'/>
<id>urn:sha1:8588719eb1bb14367464214f304b6f93452124c7</id>
<content type='text'>
This is messier than some of the other conversions because the
extensive use of 'config' as a talloc context.
</content>
</entry>
<entry>
<title>CLI: add (unused) database argument to subcommands.</title>
<updated>2021-02-06T23:05:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-12-21T12:55:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=319efe21c9d2754c99951cecc71184faf7ca9054'/>
<id>urn:sha1:319efe21c9d2754c99951cecc71184faf7ca9054</id>
<content type='text'>
This will allow transitioning individual subcommands to the new
configuration framework. Eventually when they are all converted we can
remove the notmuch_config_t * argument.

For now, live with the parameter shadowing in some some subcommands;
it will go away when they are converted.
</content>
</entry>
<entry>
<title>cli/reply: Ignore PKCS#7 wrapper parts when replying</title>
<updated>2020-05-23T01:11:25Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T22:29:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1b9f4a9863003955e6a757a6eeb8b6926d60c896'/>
<id>urn:sha1:1b9f4a9863003955e6a757a6eeb8b6926d60c896</id>
<content type='text'>
When composing a reply, no one wants to see this line in the proposed
message:

    Non-text part: application/pkcs7-mime

So we hide it, the same way we hide PGP/MIME cruft.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
</feed>
