--- /dev/null
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 006E8431FB6\r
+ for <notmuch@notmuchmail.org>; Tue, 6 May 2014 01:13:31 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 7pnAHP7vXgnV for <notmuch@notmuchmail.org>;\r
+ Tue, 6 May 2014 01:13:07 -0700 (PDT)\r
+Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net\r
+ [87.98.215.224]) (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 3241A431FAE\r
+ for <notmuch@notmuchmail.org>; Tue, 6 May 2014 01:13:07 -0700 (PDT)\r
+Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim\r
+ 4.72) (envelope-from <david@tethera.net>)\r
+ id 1WhaUN-00066W-1x; Tue, 06 May 2014 08:12:35 +0000\r
+Received: (nullmailer pid 2658 invoked by uid 1000); Tue, 06 May 2014\r
+ 08:12:16 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: notmuch@notmuchmail.org\r
+Subject: notmuch release 0.18 now available\r
+User-Agent: Notmuch/0.18 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Tue, 06 May 2014 17:12:15 +0900\r
+Message-ID: <87r447com8.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256;\r
+ protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 06 May 2014 08:13:31 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+\r
+Where to obtain notmuch 0.18\r
+===========================\r
+ http://notmuchmail.org/releases/notmuch-0.18.tar.gz\r
+\r
+Which can be verified with:\r
+\r
+ http://notmuchmail.org/releases/notmuch-0.18.tar.gz.sha1\r
+ bfbcdc340c4b0d544904b3a8ba70be4e819859d9 notmuch-0.18.tar.gz\r
+\r
+ http://notmuchmail.org/releases/notmuch-0.18.tar.gz.sha1.asc\r
+ (signed by David Bremner)\r
+\r
+What's new in notmuch 0.18\r
+=========================\r
+\r
+Overview\r
+--------\r
+\r
+This new release includes some enhancements to searching for messages\r
+by filesystem location (`folder:` and `path:` prefixes under *General*\r
+below). Saved searches in *Emacs* have also been enhanced to allow\r
+distinct search orders for each one. Another enhancement to the\r
+*Emacs* interface is that replies to encrypted messages are now\r
+encrypted, reducing the risk of unintentional information disclosure.\r
+The default dump output format has changed to the more robust\r
+`batch-tag` format. The previously deprecated parsing of single\r
+message mboxes has been removed. For detailed release notes, see\r
+below.\r
+\r
+General\r
+-------\r
+\r
+The `folder:` search prefix now requires an exact match\r
+\r
+ The `folder:` prefix has been changed to search for email messages\r
+ by the exact, case sensitive maildir or MH folder name. Wildcard\r
+ matching (`folder:foo*`) is no longer supported. The new behaviour\r
+ allows for more accurate mail folder based searches, makes it\r
+ possible to search for messages in the top-level folder, and should\r
+ lead to less surprising results than the old behaviour. Users are\r
+ advised to see the `notmuch-search-terms` manual page for details,\r
+ and review how the change affects their existing `folder:` searches.\r
+\r
+There is a new `path:` search prefix.\r
+\r
+ The new `path:` search prefix complements the `folder:` prefix. The\r
+ `path:` prefix searches for email messages that are in particular\r
+ directories within the mail store, optionally recursively using a\r
+ special syntax. See the `notmuch-search-terms` manual page for\r
+ details.\r
+\r
+Notmuch database upgrade due to `folder:` and `path:` changes\r
+\r
+ The above mentioned changes to the `folder:` prefix and the addition\r
+ of `path:` prefix require a Notmuch database upgrade. This will be\r
+ done automatically, without prompting on the next time `notmuch new`\r
+ is run after the upgrade. The upgrade is not reversible, and the\r
+ upgraded database will not be readable by older versions of\r
+ Notmuch. As a safeguard, a database dump will be created in the\r
+ `.notmuch` directory before upgrading.\r
+\r
+Library changes\r
+---------------\r
+\r
+Notmuch database upgrade\r
+\r
+ The libnotmuch consumers are reminded to handle database upgrades\r
+ properly, either by relying on running `notmuch new`, or checking\r
+ `notmuch_database_needs_upgrade()` and calling\r
+ `notmuch_database_upgrade()` as necessary. This has always been the\r
+ case, but in practise there have been no database upgrades in any\r
+ released version of Notmuch before now.\r
+\r
+Support for indexing mbox files has been dropped\r
+\r
+ There has never been proper support for mbox files containing\r
+ multiple messages, and the support for single-message mbox files has\r
+ been deprecated since Notmuch 0.15. The support has now been\r
+ dropped, and all mbox files will be rejected during indexing.\r
+\r
+Message header parsing changes\r
+\r
+ Notmuch previously had an internal parser for message headers. The\r
+ parser has now been dropped in favour of letting GMime parse both\r
+ the headers and the message MIME structure at the same pass. This is\r
+ mostly an internal change, but the GMime parser is stricter in its\r
+ interpretation of the headers. This may result in messages with\r
+ slightly malformed message headers being now rejected.\r
+\r
+Command-Line Interface\r
+----------------------\r
+\r
+`notmuch dump` now defaults to `batch-tag` format\r
+\r
+ The old format is still available with `--format=sup`.\r
+\r
+`notmuch new` has a --quiet option\r
+\r
+ This option suppresses the progress and summary reports.\r
+\r
+`notmuch insert` respects maildir.synchronize_flags config option\r
+\r
+ Do not synchronize tags to maildir flags in `notmuch insert` if the\r
+ user does not want it.\r
+\r
+The commands set consistent exit status codes on failures\r
+\r
+ The cli commands now consistently set exit status of 1 on failures,\r
+ except where explicitly otherwise noted. The notable expections are\r
+ the status codes for format version mismatches for commands that\r
+ support formatted output.\r
+\r
+Bug fix for checking configured new.tags for invalid tags\r
+\r
+ `notmuch new` and `notmuch insert` now check the user configured\r
+ new.tags for invalid tags, and refuse to apply them, similar to\r
+ `notmuch tag`. Invalid tags are currently the empty string and tags\r
+ starting with `-`.\r
+\r
+Emacs Interface\r
+---------------\r
+\r
+Init file\r
+\r
+ If the file pointed by new variable `notmuch-init-file` (typically\r
+ `~/.emacs.d/notmuch-config.el`) exists, it is loaded at the end of\r
+ `notmuch.el`. Users can put their personal notmuch emacs lisp based\r
+ configuration/customization items there instead of filling\r
+ `~/.emacs` with these.\r
+\r
+Changed format for saved searches\r
+\r
+ The format for `notmuch-saved-searches` has changed, but old style\r
+ saved searches are still supported. The new style means that a saved\r
+ search can store the desired sort order for the search, and it can\r
+ store a separate query to use for generating the count notmuch\r
+ shows.\r
+\r
+ The variable is fully customizable and any configuration done\r
+ through customize should *just work*, with the additional options\r
+ mentioned above. For manual customization see the documentation for\r
+ `notmuch-saved-searches`.\r
+\r
+ IMPORTANT: a new style notmuch-saved-searches variable will break\r
+ previous versions of notmuch-emacs (even search will not work); to\r
+ fix remove the customization for notmuch-saved-searches.\r
+\r
+ If you have a custom saved search sort function (not unsorted or\r
+ alphabetical) then the sort function will need to be\r
+ modified. Replacing (car saved-search) by (notmuch-saved-search-get\r
+ saved-search :name) and (cdr saved-search) by\r
+ (notmuch-saved-search-get saved-search :query) should be sufficient.\r
+\r
+The keys of `notmuch-tag-formats` are now regexps\r
+\r
+ Previously, the keys were literal strings. Customized settings of\r
+ `notmuch-tag-formats` will continue to work as before unless tags\r
+ contain regexp special characters like `.` or `*`.\r
+\r
+Changed tags are now shown in the buffer\r
+\r
+ Previously tag changes made in a buffer were shown immediately. In\r
+ some cases (particularly automatic tag changes like marking read)\r
+ this made it hard to see what had happened (e.g., whether the\r
+ message had been unread).\r
+\r
+ The changes are now shown explicitly in the buffer: by default\r
+ deleted tags are displayed with red strike-through and added tags\r
+ are displayed underlined in green (inverse video is used for deleted\r
+ tags if the terminal does not support strike-through).\r
+\r
+ The variables `notmuch-tag-deleted-formats` and\r
+ `notmuch-tag-added-formats`, which have the same syntax as\r
+ `notmuch-tag-formats`, allow this to be customized.\r
+\r
+ Setting `notmuch-tag-deleted-formats` to `'((".*" nil))` and\r
+ `notmuch-tag-added-formats` to `'((".*" tag))` will give the old\r
+ behavior of hiding deleted tags and showing added tags identically\r
+ to tags already present.\r
+\r
+Version variable\r
+\r
+ The new, build-time generated variable `notmuch-emacs-version` is used\r
+ to distinguish between notmuch cli and notmuch emacs versions.\r
+ The function `notmuch-hello-versions` (bound to 'v' in notmuch-hello\r
+ window) prints both notmuch cli and notmuch emacs versions in case\r
+ these differ from each other.\r
+ This is especially useful when using notmuch remotely.\r
+\r
+Ido-completing-read initialization in Emacs 23\r
+\r
+ `ido-completing-read` in Emacs 23 versions 1 through 3 freezes unless\r
+ it is initialized. Defadvice-based *Ido* initialization is defined\r
+ for these Emacs versions.\r
+\r
+Bug fix for saved searches with newlines in them\r
+\r
+ Split lines confuse `notmuch count --batch`, so we remove embedded\r
+ newlines before calling notmuch count.\r
+\r
+Bug fixes for sender identities\r
+\r
+ Previously, Emacs would rewrite some sender identities in unexpected\r
+ and undesirable ways. Now it will use identities exactly as\r
+ configured in `notmuch-identities`.\r
+\r
+Replies to encrypted messages will be encrypted by default\r
+\r
+ In the interest of maintaining confidentiality of communications,\r
+ the Notmuch Emacs interface now automatically adds the mml tag to\r
+ encrypt replies to encrypted messages. This should make it less\r
+ likely to accidentally reply to encrypted messages in plain text.\r
+\r
+Reply pushes mark before signature\r
+\r
+ We push mark and set point on reply so that the user can easily cut\r
+ the quoted text. The mark is now pushed before the signature, if\r
+ any, instead of end of buffer so the signature is preserved.\r
+\r
+Message piping uses the originating buffer's working directory\r
+\r
+ `notmuch-show-pipe-message` now uses the originating buffer's\r
+ current default directory instead of that of the `*notmuch-pipe*`\r
+ buffer's.\r
+\r
+nmbug\r
+-----\r
+\r
+nmbug adds a `clone` command for setting up the initial repository and\r
+uses `@{upstream}` instead of `FETCH_HEAD` to track upstream changes.\r
+\r
+ The `@{upstream}` change reduces ambiguity when fetching multiple\r
+ branches, but requires existing users update their `NMBGIT`\r
+ repository (usually `~/.nmbug`) to distinguish between local and\r
+ remote-tracking branches. The easiest way to do this is:\r
+\r
+ 1. If you have any purely local commits (i.e. they aren't in the\r
+ nmbug repository on nmbug.tethera.net), push them to a remote\r
+ repository. We'll restore them from the backup in step 4.\r
+ 2. Remove your `NMBGIT` repository (e.g. `mv .nmbug .nmbug.bak`).\r
+ 3. Use the new `clone` command to create a fresh clone:\r
+\r
+ nmbug clone http://nmbug.tethera.net/git/nmbug-tags.git\r
+\r
+ 4. If you had local commits in step 1, add a remote for that\r
+ repository and fetch them into the new repository.\r
+\r
+What is notmuch\r
+===============\r
+Notmuch is a system for indexing, searching, reading, and tagging\r
+large collections of email messages in maildir or mh format. It uses\r
+the Xapian library to provide fast, full-text search with a convenient\r
+search syntax.\r
+\r
+For more about notmuch, see http://notmuchmail.org\r
+\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1\r
+\r
+iQGcBAEBCAAGBQJTaJlfAAoJEPIClx2kp54sI3AL/02OOVzIHYO75gkk0IPNrzw0\r
+Tt6mzcMTzeyKuCtTKUvelL5gOXgUpDLZm0IjkKcX2j6azdTqlT1c1xK+6vAqEeOO\r
+T4ad61qUuGGodzkXtjKzsi+wiiIlxlRAUcIRYmMeRrIdL7Q28HTd58erTfM++mN6\r
+ft4go7RrAVpKbhhpNQ+WnQR0BVFLlp31OJxqCWo3SlujCiqWEMellYFbuqT08q1p\r
+NO2wn+3zDcbkzQ2ZWyIVtt2Ooyk8S/uho7Dy3cVqUqisaqc6/7h4U8DiaNMM49ci\r
+lgxEiAjrJrDbESh8vDQc/DMuIF+uFAVhL6svbJZyf9mvKehkx29YbhndGKHqKDWJ\r
+A8X3WmQc2u64fW5sgR9cvVes8faLhLA7ogr+z5hmatnUAbnK6Df8O4lHcBNo3V7R\r
+xrBuMXNswE7F/WSVHtMxi6vRpGFieE7oak6Y9IhbGkgPZx+ZsnaBqpbc55yHAo3W\r
+M0ZRwWpi+AnKWR/a2TdGz/siPnaP01hIR39oyePo+w==\r
+=Pjpq\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
projects / notmuch-archives.git / commitdiff