<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-reply.c, branch 0.12</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.12</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.12'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-02-12T16:58:20Z</updated>
<entry>
<title>cli: use notmuch_bool_t for boolean fields in notmuch_show_params_t</title>
<updated>2012-02-12T16:58:20Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-02-06T19:57:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c9c5a6f70c8371809f3b079e1aba3de3b4a13f6b'/>
<id>urn:sha1:c9c5a6f70c8371809f3b079e1aba3de3b4a13f6b</id>
<content type='text'>
Use notmuch_bool_t instead of int for entire_thread, raw, and decrypt
boolean fields in notmuch_show_params_t. No functional changes.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>show: Introduce mime_node formatter callback</title>
<updated>2012-01-25T11:21:40Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-23T23:33:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7430a42e23ee775818f84ed75f417302da694152'/>
<id>urn:sha1:7430a42e23ee775818f84ed75f417302da694152</id>
<content type='text'>
This callback is the gateway to the new mime_node_t-based formatters.
This maintains backwards compatibility so the formatters can be
transitioned one at a time.  Once all formatters are converted, the
formatter structure can be reduced to only message_set_{start,sep,end}
and part, most of show_message can be deleted, and all of
show-message.c can be deleted.
</content>
</entry>
<entry>
<title>Add compatibility with gmime 2.6</title>
<updated>2012-01-21T12:52:34Z</updated>
<author>
<name>Thomas Jost</name>
<email>schnouki@schnouki.net</email>
</author>
<published>2012-01-20T09:39:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=00b5623d1a21d886b564d031e30749e5d02e4ae6'/>
<id>urn:sha1:00b5623d1a21d886b564d031e30749e5d02e4ae6</id>
<content type='text'>
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.

This is mostly based on id:"8762i8hrb9.fsf@bookbinder.fernseed.info".

This was tested against both gmime 2.6.4 and 2.4.31. With gmime 2.4.31, the
crypto tests all work fine (as expected). With gmime 2.6.4, one crypto test is
currently broken (signature verification with signer key unavailable), most
likely because of a bug in gmime which will hopefully be fixed in a future
version.
</content>
</entry>
<entry>
<title>cli: pick the user's address in a group list as from address</title>
<updated>2012-01-17T01:06:34Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-01-14T21:49:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=982096d79df8d47ac62d9a74fa0a9baa9c008812'/>
<id>urn:sha1:982096d79df8d47ac62d9a74fa0a9baa9c008812</id>
<content type='text'>
Messages received to a group list were not replied to using the from
address in the list. Fix it.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>cli: add support for replying just to the sender in "notmuch reply"</title>
<updated>2012-01-14T15:10:28Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-01-14T14:46:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0f8148e920810349df207414e40b9489dc246c37'/>
<id>urn:sha1:0f8148e920810349df207414e40b9489dc246c37</id>
<content type='text'>
Add new option --reply-to=(all|sender) to "notmuch reply" to select whether
to reply to all (sender and all recipients), or just sender. Reply to all
remains the default.

Credits to Mark Walters &lt;markwalters1009@gmail.com&gt; for his similar earlier
work where I picked up the basic idea of handling reply-to-sender in
add_recipients_from_message(). All bugs are mine, though.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>cli: slightly refactor "notmuch reply" address scanning functions</title>
<updated>2012-01-14T15:10:17Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-01-14T14:46:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fb1c016cb5ec5263b24c9210c26f8e6f6cfd0942'/>
<id>urn:sha1:fb1c016cb5ec5263b24c9210c26f8e6f6cfd0942</id>
<content type='text'>
Slightly refactor "notmuch reply" recipient and user from address scanning
functions in preparation for reply-to-sender feature.

Add support for not adding recipients at all (just scan for user from
address), and returning the number of recipients added.

No externally visible functional changes.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>cli: convert "notmuch reply" to use the new argument parser</title>
<updated>2012-01-09T10:45:02Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-01-05T20:25:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2d1385e141b1799b4b3942a3fe2dcbcdbf92dc38'/>
<id>urn:sha1:2d1385e141b1799b4b3942a3fe2dcbcdbf92dc38</id>
<content type='text'>
Use the new notmuch argument parser to handle arguments in "notmuch
reply". There should be no functional changes.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>cli: fix use of uninitialized variable in "notmuch reply"</title>
<updated>2012-01-09T10:44:47Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-01-05T20:25:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=230c2ed35750d57203977a159cfb0da21118032d'/>
<id>urn:sha1:230c2ed35750d57203977a159cfb0da21118032d</id>
<content type='text'>
notmuch_show_params_t params is only initialized partially in
notmuch_reply_command(). The only field that is used uninitialized is
params.decrypt. It is usually non-zero, making "notmuch reply" on encrypted
messages work by coincidence.

Initialize params properly, and set params.decrypt as needed.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>show: Pass notmuch_message_t instead of path to show_message_body.</title>
<updated>2011-12-26T02:17:27Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2011-12-24T18:52:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=36f7fe5a1c83f3f0dd8fc883db558ab058b974f3'/>
<id>urn:sha1:36f7fe5a1c83f3f0dd8fc883db558ab058b974f3</id>
<content type='text'>
In addition to simplifying the code, we'll need the notmuch_message_t*
in show_message_body shortly.
</content>
</entry>
<entry>
<title>cli: change argument parsing convention for subcommands</title>
<updated>2011-10-22T22:42:54Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-10-21T12:19:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=61f0a5b8ee2adf540106a09c5f83fe634da6beb3'/>
<id>urn:sha1:61f0a5b8ee2adf540106a09c5f83fe634da6beb3</id>
<content type='text'>
previously we deleted the subcommand name from argv before passing to
the subcommand. In this version, the deletion is done in the actual
subcommands. Although this causes some duplication of code, it allows
us to be more flexible about how we parse command line arguments in
the subcommand, including possibly using off-the-shelf routines like
getopt_long that expect the name of the command in argv[0].
</content>
</entry>
</feed>
