<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-dump.c, branch 0.10.1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.10.1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.10.1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2011-10-22T22:42:54Z</updated>
<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>
<entry>
<title>notmuch-dump: deprecate use of output file argument.</title>
<updated>2011-10-16T22:59:53Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-10-10T13:44:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=53b397acfcd6b6372372593cc9047ee1a9599afd'/>
<id>urn:sha1:53b397acfcd6b6372372593cc9047ee1a9599afd</id>
<content type='text'>
We print an intentionally non-specific message on stderr, since it
isn't clear if there will be some global output file argument to
replace.

We update the test suite atomically, since it relies on having the
same text in two files.
</content>
</entry>
<entry>
<title>notmuch-dump: treat any remaining arguments after the filename as search terms</title>
<updated>2011-10-16T22:59:53Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-10-09T14:12:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=09beff1def1daa9887679723205855ff7da8a297'/>
<id>urn:sha1:09beff1def1daa9887679723205855ff7da8a297</id>
<content type='text'>
The main motivation here is allow the fast dumping of tag data for
messages having certain tags.  In practice it seems too slow to pipe
dump to grep.

All dump-restore tests should be working now, so we update test/dump-restore
accordingly
</content>
</entry>
<entry>
<title>notmuch-dump: update handling of file name argument</title>
<updated>2011-10-16T22:59:53Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-10-09T13:57:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ff2cd7a789b81e76d2279ac8a13a06172c6d8279'/>
<id>urn:sha1:ff2cd7a789b81e76d2279ac8a13a06172c6d8279</id>
<content type='text'>
We permit -- as an "option processing terminator".

Currently this does not do anything useful, but we plan to add
search terms after the --.
</content>
</entry>
<entry>
<title>lib: Rename iterator functions to prepare for reverse iteration.</title>
<updated>2010-03-09T17:22:29Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-03-09T17:22:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e5d2f22db290a830c0267f34b519c6138af00ed'/>
<id>urn:sha1:4e5d2f22db290a830c0267f34b519c6138af00ed</id>
<content type='text'>
We rename 'has_more' to 'valid' so that it can function whether
iterating in a forward or reverse direction. We also rename
'advance' to 'move_to_next' to setup parallel naming with
the proposed functions 'move_to_first', 'move_to_last', and
'move_to_previous'.
</content>
</entry>
<entry>
<title>lib/query: Drop the first and max_messages arguments from search_messages.</title>
<updated>2009-11-24T04:25:13Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-24T04:25:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=94eb9aacd40a8aa133f64bbe5ed71c0138fb5ed9'/>
<id>urn:sha1:94eb9aacd40a8aa133f64bbe5ed71c0138fb5ed9</id>
<content type='text'>
These only existed to support the chunky-searching hack, but that
was recently dropped anyway.
</content>
</entry>
<entry>
<title>Rename NOTMUCH_DATABASE_MODE_WRITABLE to NOTMUCH_DATABASE_MODE_READ_WRITE</title>
<updated>2009-11-21T21:10:18Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-21T21:10:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=637f99d8f3f45867d0a856503f9f302333824c07'/>
<id>urn:sha1:637f99d8f3f45867d0a856503f9f302333824c07</id>
<content type='text'>
And correspondingly, READONLY to READ_ONLY.
</content>
</entry>
<entry>
<title>Permit opening the notmuch database in read-only mode.</title>
<updated>2009-11-21T21:04:49Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2009-11-21T19:54:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f379aa52845f5594aa6cc2e7cf131d5f57202bbf'/>
<id>urn:sha1:f379aa52845f5594aa6cc2e7cf131d5f57202bbf</id>
<content type='text'>
We only rarely need to actually open the database for writing, but we
always create a Xapian::WritableDatabase. This has the effect of
preventing searches and like whilst updating the index.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Acked-by: Carl Worth &lt;cworth@cworth.org&gt;
</content>
</entry>
<entry>
<title>libnotmuch: Underlying support for doing partial-results searches.</title>
<updated>2009-11-13T00:47:27Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-13T00:47:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=93dcc3b695e19dd36cc8f638c6e01ecbbd9a447d'/>
<id>urn:sha1:93dcc3b695e19dd36cc8f638c6e01ecbbd9a447d</id>
<content type='text'>
The library interface now allows the caller to do incremental searches,
(such as one page of results at a time). Next we'll just need to hook
this up to "notmuch search" and the emacs interface.
</content>
</entry>
<entry>
<title>Unbreak several notmuch commands after the addition of configuration.</title>
<updated>2009-11-12T04:29:30Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2009-11-12T04:29:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=13569ad6c96c3f3a653ac51274056614647ad7ef'/>
<id>urn:sha1:13569ad6c96c3f3a653ac51274056614647ad7ef</id>
<content type='text'>
All of the following commands:

	notmuch dump
	notmuch reply
	notmuch restore
	notmuch search
	notmuch show
	notmuch tag

were calling notmuch_database_open with an argument of NULL. This was
a legitimate call until the recent addition of configuration, after
which it is expected that all commands will lookup the correct path in
the configuration file. So fix all these commands to do that.

Also, while touching all of these commands, we fix them to use the
talloc context that is passed in rather than creating a local talloc
context. We also switch from using goto for return values, to doing
direct returns as soon as an error is detected, (which can be leak
free thanks to talloc).
</content>
</entry>
</feed>
