<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch.1, branch 0.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-04-02T08:43:03Z</updated>
<entry>
<title>notmuch: Add a 'part' subcommand</title>
<updated>2010-04-02T08:43:03Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2010-03-24T07:21:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2e9c7aba99598eafd7b5fc52897da14ea13af216'/>
<id>urn:sha1:2e9c7aba99598eafd7b5fc52897da14ea13af216</id>
<content type='text'>
A new 'part' subcommand allows the user to extract a single part from
a MIME message. Usage:
  notmuch part --part=&lt;n&gt; &lt;search terms&gt;
The search terms must match only a single message
(e.g. id:foo@bar.com). The part number specified refers to the part
identifiers output by `notmuch show'. The content of the part is
written the stdout with no formatting or identification marks. It is
not JSON formatted.
</content>
</entry>
<entry>
<title>Add is:&lt;tag&gt; as a synonym for tag:&lt;tag&gt; in search terms.</title>
<updated>2010-03-10T00:03:58Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-03-10T00:03:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e3046c688be7a28e7dcfbce5fa54074917fd9904'/>
<id>urn:sha1:e3046c688be7a28e7dcfbce5fa54074917fd9904</id>
<content type='text'>
I like the readability of this, it provides compatibility with people
trained in this syntax by sup, and it even saves one character.
</content>
</entry>
<entry>
<title>Add an "--format=(json|text)" command-line option to both notmuch-search and notmuch-show.</title>
<updated>2010-02-23T20:01:12Z</updated>
<author>
<name>Scott Robinson</name>
<email>scott@quadhome.com</email>
</author>
<published>2009-12-31T15:17:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6ce2bf68f53fec4302121763e588c33c7cd86a9c'/>
<id>urn:sha1:6ce2bf68f53fec4302121763e588c33c7cd86a9c</id>
<content type='text'>
In the case of notmuch-show, "--format=json" also implies
"--entire-thread" as the thread structure is implicit in the emitted
document tree.

As a coincidence to the implementation, multipart message ID numbers are
now incremented with each part printed. This changes the previous
semantics, which were unclear and not necessary related to the actual
ordering of the message parts.
</content>
</entry>
<entry>
<title>notmuch.1: Use bold and indentation for the NOTMUCH_CONFIG variable.</title>
<updated>2010-02-23T19:21:41Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-23T19:21:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6365f156c8a282840ab2482d00f4677ad148962b'/>
<id>urn:sha1:6365f156c8a282840ab2482d00f4677ad148962b</id>
<content type='text'>
This seems to be the standard method of formatting an environment
variable section within a man page.
</content>
</entry>
<entry>
<title>Add ENVIRONMENT VARIABLES section to the man page</title>
<updated>2010-02-23T19:14:09Z</updated>
<author>
<name>James Westby</name>
<email>jw+debian@jameswestby.net</email>
</author>
<published>2009-12-19T13:12:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a696119756fb13ef875d01134a84a25ac846a7bb'/>
<id>urn:sha1:a696119756fb13ef875d01134a84a25ac846a7bb</id>
<content type='text'>
Briefly describe the NOTMUCH_CONFIG variable there.
</content>
</entry>
<entry>
<title>notmuch new: Remove hack to ignore read-only directories in mail store.</title>
<updated>2010-01-06T18:32:05Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-12-14T23:57:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3a9c3ec9e719f0e5adefe0ceafffeb34c7a3917e'/>
<id>urn:sha1:3a9c3ec9e719f0e5adefe0ceafffeb34c7a3917e</id>
<content type='text'>
This was really the last thing keeping the initial run of "notmuch
new" being different from all other runs. And I'm taking a fresh
look at the performance of "notmuch new" anyway, so I think we can
safely drop this optimization.
</content>
</entry>
<entry>
<title>notmuch.1: Document the new --entire-thread option to "notmuch show".</title>
<updated>2009-12-03T00:14:41Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-12-02T23:48:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=63c503a5ac1a8441b32c615ea91a0dac5f8507c4'/>
<id>urn:sha1:63c503a5ac1a8441b32c615ea91a0dac5f8507c4</id>
<content type='text'>
This was added to "notmuch help" earlier, but not to the man page.
Add it there, and use consistent wording in both places.
</content>
</entry>
<entry>
<title>Documentation for notmuch reply --format=(default|headers-only)</title>
<updated>2009-11-28T20:13:02Z</updated>
<author>
<name>Jed Brown</name>
<email>jed@59A2.org</email>
</author>
<published>2009-11-28T17:56:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a2a522a758518d19e0cf4b96cf3c55287b0fbf4f'/>
<id>urn:sha1:a2a522a758518d19e0cf4b96cf3c55287b0fbf4f</id>
<content type='text'>
Signed-off-by: Jed Brown &lt;jed@59A2.org&gt;
</content>
</entry>
<entry>
<title>notmuch search: Remove the chunked-searching hack.</title>
<updated>2009-11-24T04:17:37Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-24T04:12:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1fd8b7866f189a66e4491b01452f476371759f91'/>
<id>urn:sha1:1fd8b7866f189a66e4491b01452f476371759f91</id>
<content type='text'>
This was a poor workaround around the fact that the existing
notmuch_threads_t object is implemented poorly. It's got a fine
iterartor-based interface, but the implementation does all of the
work up-front in _create rather than doing the work incrementally
while iterating.

So to start fixing this, first get rid of all the hacks we had working
around this. This drops the --first and --max-threads options from the
search command, (but hopefully nobody was using them
anyway---notmuch.el certainly wasn't).
</content>
</entry>
<entry>
<title>Add rudimentary date-based search.</title>
<updated>2009-11-23T16:17:08Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-23T15:58:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=793cbf80495b8230e0b4de6ac609e2ca88b7dd4b'/>
<id>urn:sha1:793cbf80495b8230e0b4de6ac609e2ca88b7dd4b</id>
<content type='text'>
The rudimentary aspect here is that the date ranges are specified with
UNIX timestamp values (number of seconds since 1970-01-01 UTC). One
thing that can help here is using the date program to determins
timestamps, such as:

	$(date +%s -d 2009-10-01)..$(date +%s)

Long-term, we'll probably need to do our own query parsing to be able
to support directly-specified dates and also relative expressions like
"since:'2 months ago'".
</content>
</entry>
</feed>
