notmuch/database.cc, branch master thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=master 2009-11-10T00:24:03Z libify: Move library sources down into lib directory. 2009-11-10T00:24:03Z Carl Worth cworth@cworth.org 2009-11-10T00:12:28Z urn:sha1:146549321044615d9aef2b30cedccda9c49f3f38 A "make" invocation still works from the top-level, but not from down inside the lib directory yet. add_message: Fix crash for file recognized as not email. 2009-11-09T21:43:59Z Carl Worth cworth@cworth.org 2009-11-09T21:43:59Z urn:sha1:39429339624f8d29db8f523d52a81c70001ebebe This crash was introduced sometime recently, as previously things worked fine when notmuch detected that a file is not an email. We're definitely overdue for that test suite. add_message: Start storing In-Reply-To information in the database. 2009-11-06T17:34:21Z Carl Worth cworth@cworth.org 2009-11-06T17:34:21Z urn:sha1:1eec45659b1f647c862667b045eb27a691d0f11e We'll use this eventually for properly nesting messages in the output of "notmuch show", etc. notmuch show: Add a one-line summary of the message before the header. 2009-10-30T00:30:56Z Carl Worth cworth@cworth.org 2009-10-29T23:06:27Z urn:sha1:41c7ad2c91e56bfc0b2fefa0be303605d34f4042 The idea here is that a client could usefully display just this one line while optionally hiding the other header fields. Fix add_message and get_filename to strip/re-add the database path. 2009-10-28T23:51:56Z Carl Worth cworth@cworth.org 2009-10-28T23:50:14Z urn:sha1:a1135f0b7e67db7056a4ef02d61b8ad0ec46e88b We now store only a relative path inside the database so the database is not nicely relocatable. notmuch_database_add_message: Sanity check the file as the first thing 2009-10-28T20:35:10Z Carl Worth cworth@cworth.org 2009-10-28T20:35:10Z urn:sha1:cfa228a3d4b300df3551e811028508d3de5cd81c This avoids us wasting a bunch of time doing an expensive SHA-1 over a large file only to discover later that it doesn't even *look* like an email message. Tweak formatting of internal error messages. 2009-10-28T20:13:23Z Carl Worth cworth@cworth.org 2009-10-28T19:46:50Z urn:sha1:81861514c9a86350d24322c1de80b284bd2c1033 Was neglecting to print the phrase "Internal error: " before, and for the duplicate message-ID error it's nice to actually see the duplicate IDs. index: Store "Full Name <user@example.com>" addressses in the database 2009-10-28T20:09:08Z Carl Worth cworth@cworth.org 2009-10-28T20:09:08Z urn:sha1:3a91df21caddd952fe9a3e3ba8128e781a3f6ec5 We put these is as a separate term so that they can be extracted. We don't actually need this for searching, since typing an email address in as a search term will already trigger a phrase search that does exactly what's wanted. Add full-text indexing using the GMime library for parsing. 2009-10-28T19:50:10Z Carl Worth cworth@cworth.org 2009-10-28T17:42:07Z urn:sha1:f9bbd7baa07110c7f345c8413e2426d00382cb1c This is based on the old notmuch-index-message.cc from early in the history of notmuch, but considerably cleaned up now that we have some experience with Xapian and know just what we want to index, (rather than just blindly trying to index exactly what sup does). This does slow down notmuch_database_add_message a *lot*, but I've got some ideas for getting some time back. Fix segfault in case of the database lock not being available. 2009-10-28T06:57:37Z Carl Worth cworth@cworth.org 2009-10-28T06:57:37Z urn:sha1:07aa759b68f3198e565385eb23736984bb378d0f We were nicely reporting the lock-aquisition failure, but then marching along trying to use the database object and just crashing badly. So don't do that.