thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.23.3 2016-06-11T16:01:30Z 2016-06-11T16:01:30Z Tomi Ollila tomi.ollila@iki.fi 2016-06-09T19:35:12Z urn:sha1:1e96445cb5dc333e22b9ce01245902ba23fdb437 Setting locale environment variables (LC_* and LANG) to e.g. en_US.utf8 works fine on Linux, and that is what locale -a returns (in Linux). However this does not work e.g. in some *BSD systems. In these systems, en_US.UTF-8 works. This also works in Linux systems (which may look like a surprising thing on the first sight(*)). But that *UTF-8 format seems to be widely used in the Linux system: Grep it through the files in /etc/, for example. Easy way to test: Run the following command lines. First should complain about setting locale failed, and second should not. $ LC_ALL=en_US.UTF-1 perl -e '' $ LC_ALL=en_US.UTF-8 perl -e '' (*) and who knows what the "standard" is... 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-06-05T11:27:13Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-06-02T16:26:13Z urn:sha1:554b90b58e367ada5fdad3165c76673458f65434 2016-03-28T12:29:42Z David Bremner david@tethera.net 2016-03-27T20:25:11Z urn:sha1:9bbc54bd406fc218a5463efe9a127aee461fb47b Lines starting with # have always (for a long time, anyway) been ignored by notmuch-restore, but have not been generated by notmuch-dump previously. In order to make nmbug robust against such output, ignore comment lines. 2016-03-24T10:41:24Z W. Trevor King wking@tremily.us 2016-01-02T06:08:04Z urn:sha1:d6cbb24fcf6ad2a4306c0913b10b1f3c574bbcaa To describe the script and config file format, so folks don't have to dig through NEWS or the script's source to get that information. The Makefile and conf.py are excerpted from the main doc/ directory with minor simplifications and adjustments. The devel/nmbug/ scripts are largely independent of notmuch, and separating the docs here allows packagers to easily build the docs and install the scripts in a separate package, without complicating notmuch's core build/install process. 2016-03-24T10:41:06Z W. Trevor King wking@tremily.us 2016-01-02T06:08:03Z urn:sha1:399c857ebaeafb3bb68caaa659b87ba371e7426b status-config.json wasn't obviously associated with the old nmubg-status, now notmuch-report. The new name is ${CONFIGURED_SCRIPT}.json, so the association should be clear. 2016-03-24T10:40:39Z W. Trevor King wking@tremily.us 2016-01-02T06:08:02Z urn:sha1:074f45e305ca511f260153d275b37826965a61c4 This script generates reports based on notmuch queries, and doesn't really have anything to do with nmbug, except for sharing the NMBGIT environment variable. 2016-03-24T10:39:57Z W. Trevor King wking@tremily.us 2016-01-02T06:07:43Z urn:sha1:88171f34ed140e0701c2101e978d993673b423d2 These are now added by nmbug-status. 2016-03-24T10:39:42Z W. Trevor King wking@tremily.us 2016-01-02T06:07:42Z urn:sha1:6c0b6c8e1c4a8ab139db3cadee26d05962c3ce2c For example: "query": ["tag:a", "tag:b or tag:c"] is now converted to: ( tag:a ) and ( tag:b or tag:c ) instead of the old: tag:a and tag:b or tag:c This helps us avoid confusion due to Xapian's higher-precedence AND [1], where the old query would be interpreted as: ( tag:a and tag:b ) or tag:c [1]: http://xapian.org/docs/queryparser.html 2016-03-24T10:39:25Z W. Trevor King wking@tremily.us 2016-01-02T06:07:41Z urn:sha1:031ca3f1bdb5e9edb9fc21779149bdfcb554a83f So you can link to archives other than Gmane. For example, I'm doing this in [1]. [1]: https://github.com/wking/nmbug-oci