notmuch/notmuch-search.c, branch 0.3

removed unused variables

2010-04-24T00:53:52Z

trivial compiler warning fix Signed-off-by: Dirk Hohndel

notmuch search: Fix timezone of timestamp in --format=json output

2010-04-23T00:12:07Z

This is one of those cases that I move love. Deleting code fixes a bug, (test suite now passes again).

lib: Rename iterator functions to prepare for reverse iteration.

2010-03-09T17:22:29Z

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'.

notmuch search: Use "thread" rather than "id" when formatting with JSON

2010-02-23T20:50:46Z

The text output uses thread:, (which is a syntax directly supported by "notmuch show"), so make the json output be "thread", "" rather than "id", "". This should help avoid confusion of thread IDs with message IDs, (which do use the "id" prefix in searches).

Add an "--format=(json|text)" command-line option to both notmuch-search and notmuch-show.

2010-02-23T20:01:12Z

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.

notmuch search: Remove the chunked-searching hack.

2009-11-24T04:17:37Z

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).

search : Extend "intial burst" optimization to return all results by chunks

2009-11-23T17:14:47Z

This way, the user gets a steady (but bursty) stream of reults. We double the chunk size each time since each successive chunk has to redo work from all previous chunks. Of course, the overall time is thereby slower, as the price we pay for increased responsiveness. With a search returning about 17000 thread results I measured a total time of 48.8 seconds before this change and 58.4 seconds afterwards.

Rename NOTMUCH_DATABASE_MODE_WRITABLE to NOTMUCH_DATABASE_MODE_READ_WRITE

2009-11-21T21:10:18Z

And correspondingly, READONLY to READ_ONLY.

Permit opening the notmuch database in read-only mode.

2009-11-21T21:04:49Z

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 Acked-by: Carl Worth

notmuch search: Avoid infinite stream of exceptions from "notmuch search"

2009-11-18T11:29:30Z

That is, give a nice error message and exit if no search terms are provided. Thanks to Priit Laes for reporting the error and providing an early version of the fix.