thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.28.4 2017-08-23T10:38:37Z 2017-08-23T10:38:37Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-08-17T23:14:25Z urn:sha1:b10ce6bc23002d48916b1b2f375480e7540e3164 We need a way to pass parameters to the indexing functionality on the first index, not just on reindexing. The obvious place is in notmuch_database_add_message. But since modifying the argument list would break both API and ABI, we needed a new name. I considered notmuch_database_add_message_with_params(), but the functionality we're talking about doesn't always add a message. It tries to index a specific file, possibly adding a message, but possibly doing other things, like adding terms to an existing message, or failing to deal with message objects entirely (e.g. because the file didn't contain a message). So i chose the function name notmuch_database_index_file. I confess i'm a little concerned about confusing future notmuch developers with the new name, since we already have a private _notmuch_message_index_file function, and the two do rather different things. But i think the added clarity for people linking against the future libnotmuch and the capacity for using index parameters makes this a worthwhile tradeoff. (that said, if anyone has another name that they strongly prefer, i'd be happy to go with it) This changeset also adjusts the tests so that we test whether the new, preferred function returns bad values (since the deprecated function just calls the new one). We can keep the deprecated n_d_add_message function around as long as we like, but at the next place where we're forced to break API or ABI we can probably choose to drop the name relatively safely. NOTE: there is probably more cleanup to do in the ruby and go bindings to complete the deprecation directly. I don't know those languages well enough to attempt a fix; i don't know how to test them; and i don't know the culture around those languages about API additions or deprecations. 2017-08-18T22:42:35Z Vladimir Panteleev notmuch@thecybershadow.net 2017-08-17T00:41:10Z urn:sha1:ca4688e103c644fa383108a79668e8e0b4dbe262 A leading / in paths in a .gitignore file matches the beginning of the path, meaning that for patterns without slashes, git will match files only in the current directory as opposed to in any subdirectory. Prefix relevant paths with / in .gitignore files, to prevent accidentally ignoring files in subdirectories and possibly slightly improve the performance of "git status". 2017-03-22T11:35:07Z David Bremner david@tethera.net 2017-02-26T21:21:35Z urn:sha1:3721bd45d72e50436ee760b03ae533d49bbb8724 This function was deprecated in notmuch 0.21. We re-use the name for a status returning version, and deprecate the _st name. 2017-03-22T11:35:07Z David Bremner david@tethera.net 2017-02-26T21:21:34Z urn:sha1:5ce8e0b11b40f733e6231d2067764e76717a341a This function was deprecated in notmuch 0.21. We re-use the name for a status returning version, and deprecate the _st name. One or two remaining uses of the (removed) non-status returning version fixed at the same time 2017-03-22T11:35:07Z David Bremner david@tethera.net 2017-02-26T21:21:32Z urn:sha1:86cbd215eb67d7b996c977352a50e70c101cb641 This function was deprecated in notmuch 0.21. We re-use the name for a status returning version, and deprecate the _st name. 2017-03-22T11:28:09Z David Bremner david@tethera.net 2017-02-26T21:21:31Z urn:sha1:1e982de508c39dae7a61403f536df74c180dfb72 This function was deprecated in notmuch 0.21. We finally remove the deprecated API, and rename the status returning version to the simpler name. The status returning is kept as a deprecated alias. 2017-03-12T12:17:29Z Tomi Ollila tomi.ollila@iki.fi 2017-03-12T11:59:13Z urn:sha1:35cdebdad0d41be58a4c705ec48fd1bb51f098eb In addition to use ${srcdir} and deliver ${NOTMUCH_SRCDIR} where needed, source from ruby bindings had to be copied to the out-of-tree target directory -- if the source files in source directory were referenced in build and there were also built object files there, those could have been considered as target files (and then not found when attempting to create bindings/ruby/notmuch.so). 2016-06-05T11:32:17Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-06-02T16:26:14Z urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb Many of the external links found in the notmuch source can be resolved using https instead of http. This changeset addresses as many as i could find, without touching the e-mail corpus or expected outputs found in tests. 2016-05-19T11:02:43Z Ludovic LANGE ll-notmuchmail@lange.nom.fr 2016-03-06T11:56:28Z urn:sha1:7e6e23c36e290d4b22b0449766a6ef2107f1ef6c The Ruby bindings were missing a way to get all the tags of the database. Now you should be able to access this with the public instance method `all_tags` of your database object. Example of use: notmuchdb = Notmuch::Database.new path, { :create => false, :mode => Notmuch::MODE_READ_ONLY } my_tags = notmuchdb.all_tags my_tags.each { |tag| print tag } my_tags.destroy! Amended by db: improve error reporting, add test 2015-10-05T22:54:12Z David Bremner david@tethera.net 2015-09-27T15:32:03Z urn:sha1:e8a828b30d099b929d2feab0154e98d06786e92e These changes should not be too surprising for users because the routines were already potentially throwing exceptions.