1 Return-Path: <david@tethera.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 006E8431FB6
\r
6 for <notmuch@notmuchmail.org>; Tue, 6 May 2014 01:13:31 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id 7pnAHP7vXgnV for <notmuch@notmuchmail.org>;
\r
16 Tue, 6 May 2014 01:13:07 -0700 (PDT)
\r
17 Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net
\r
18 [87.98.215.224]) (using TLSv1 with cipher AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 3241A431FAE
\r
21 for <notmuch@notmuchmail.org>; Tue, 6 May 2014 01:13:07 -0700 (PDT)
\r
22 Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim
\r
23 4.72) (envelope-from <david@tethera.net>)
\r
24 id 1WhaUN-00066W-1x; Tue, 06 May 2014 08:12:35 +0000
\r
25 Received: (nullmailer pid 2658 invoked by uid 1000); Tue, 06 May 2014
\r
27 From: David Bremner <david@tethera.net>
\r
28 To: notmuch@notmuchmail.org
\r
29 Subject: notmuch release 0.18 now available
\r
30 User-Agent: Notmuch/0.18 (http://notmuchmail.org) Emacs/24.3.1
\r
31 (x86_64-pc-linux-gnu)
\r
32 Date: Tue, 06 May 2014 17:12:15 +0900
\r
33 Message-ID: <87r447com8.fsf@maritornes.cs.unb.ca>
\r
35 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256;
\r
36 protocol="application/pgp-signature"
\r
37 X-BeenThere: notmuch@notmuchmail.org
\r
38 X-Mailman-Version: 2.1.13
\r
40 List-Id: "Use and development of the notmuch mail system."
\r
41 <notmuch.notmuchmail.org>
\r
42 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
43 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
44 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
45 List-Post: <mailto:notmuch@notmuchmail.org>
\r
46 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
47 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
49 X-List-Received-Date: Tue, 06 May 2014 08:13:31 -0000
\r
52 Content-Type: text/plain
\r
55 Where to obtain notmuch 0.18
\r
56 ===========================
\r
57 http://notmuchmail.org/releases/notmuch-0.18.tar.gz
\r
59 Which can be verified with:
\r
61 http://notmuchmail.org/releases/notmuch-0.18.tar.gz.sha1
\r
62 bfbcdc340c4b0d544904b3a8ba70be4e819859d9 notmuch-0.18.tar.gz
\r
64 http://notmuchmail.org/releases/notmuch-0.18.tar.gz.sha1.asc
\r
65 (signed by David Bremner)
\r
67 What's new in notmuch 0.18
\r
68 =========================
\r
73 This new release includes some enhancements to searching for messages
\r
74 by filesystem location (`folder:` and `path:` prefixes under *General*
\r
75 below). Saved searches in *Emacs* have also been enhanced to allow
\r
76 distinct search orders for each one. Another enhancement to the
\r
77 *Emacs* interface is that replies to encrypted messages are now
\r
78 encrypted, reducing the risk of unintentional information disclosure.
\r
79 The default dump output format has changed to the more robust
\r
80 `batch-tag` format. The previously deprecated parsing of single
\r
81 message mboxes has been removed. For detailed release notes, see
\r
87 The `folder:` search prefix now requires an exact match
\r
89 The `folder:` prefix has been changed to search for email messages
\r
90 by the exact, case sensitive maildir or MH folder name. Wildcard
\r
91 matching (`folder:foo*`) is no longer supported. The new behaviour
\r
92 allows for more accurate mail folder based searches, makes it
\r
93 possible to search for messages in the top-level folder, and should
\r
94 lead to less surprising results than the old behaviour. Users are
\r
95 advised to see the `notmuch-search-terms` manual page for details,
\r
96 and review how the change affects their existing `folder:` searches.
\r
98 There is a new `path:` search prefix.
\r
100 The new `path:` search prefix complements the `folder:` prefix. The
\r
101 `path:` prefix searches for email messages that are in particular
\r
102 directories within the mail store, optionally recursively using a
\r
103 special syntax. See the `notmuch-search-terms` manual page for
\r
106 Notmuch database upgrade due to `folder:` and `path:` changes
\r
108 The above mentioned changes to the `folder:` prefix and the addition
\r
109 of `path:` prefix require a Notmuch database upgrade. This will be
\r
110 done automatically, without prompting on the next time `notmuch new`
\r
111 is run after the upgrade. The upgrade is not reversible, and the
\r
112 upgraded database will not be readable by older versions of
\r
113 Notmuch. As a safeguard, a database dump will be created in the
\r
114 `.notmuch` directory before upgrading.
\r
119 Notmuch database upgrade
\r
121 The libnotmuch consumers are reminded to handle database upgrades
\r
122 properly, either by relying on running `notmuch new`, or checking
\r
123 `notmuch_database_needs_upgrade()` and calling
\r
124 `notmuch_database_upgrade()` as necessary. This has always been the
\r
125 case, but in practise there have been no database upgrades in any
\r
126 released version of Notmuch before now.
\r
128 Support for indexing mbox files has been dropped
\r
130 There has never been proper support for mbox files containing
\r
131 multiple messages, and the support for single-message mbox files has
\r
132 been deprecated since Notmuch 0.15. The support has now been
\r
133 dropped, and all mbox files will be rejected during indexing.
\r
135 Message header parsing changes
\r
137 Notmuch previously had an internal parser for message headers. The
\r
138 parser has now been dropped in favour of letting GMime parse both
\r
139 the headers and the message MIME structure at the same pass. This is
\r
140 mostly an internal change, but the GMime parser is stricter in its
\r
141 interpretation of the headers. This may result in messages with
\r
142 slightly malformed message headers being now rejected.
\r
144 Command-Line Interface
\r
145 ----------------------
\r
147 `notmuch dump` now defaults to `batch-tag` format
\r
149 The old format is still available with `--format=sup`.
\r
151 `notmuch new` has a --quiet option
\r
153 This option suppresses the progress and summary reports.
\r
155 `notmuch insert` respects maildir.synchronize_flags config option
\r
157 Do not synchronize tags to maildir flags in `notmuch insert` if the
\r
158 user does not want it.
\r
160 The commands set consistent exit status codes on failures
\r
162 The cli commands now consistently set exit status of 1 on failures,
\r
163 except where explicitly otherwise noted. The notable expections are
\r
164 the status codes for format version mismatches for commands that
\r
165 support formatted output.
\r
167 Bug fix for checking configured new.tags for invalid tags
\r
169 `notmuch new` and `notmuch insert` now check the user configured
\r
170 new.tags for invalid tags, and refuse to apply them, similar to
\r
171 `notmuch tag`. Invalid tags are currently the empty string and tags
\r
179 If the file pointed by new variable `notmuch-init-file` (typically
\r
180 `~/.emacs.d/notmuch-config.el`) exists, it is loaded at the end of
\r
181 `notmuch.el`. Users can put their personal notmuch emacs lisp based
\r
182 configuration/customization items there instead of filling
\r
183 `~/.emacs` with these.
\r
185 Changed format for saved searches
\r
187 The format for `notmuch-saved-searches` has changed, but old style
\r
188 saved searches are still supported. The new style means that a saved
\r
189 search can store the desired sort order for the search, and it can
\r
190 store a separate query to use for generating the count notmuch
\r
193 The variable is fully customizable and any configuration done
\r
194 through customize should *just work*, with the additional options
\r
195 mentioned above. For manual customization see the documentation for
\r
196 `notmuch-saved-searches`.
\r
198 IMPORTANT: a new style notmuch-saved-searches variable will break
\r
199 previous versions of notmuch-emacs (even search will not work); to
\r
200 fix remove the customization for notmuch-saved-searches.
\r
202 If you have a custom saved search sort function (not unsorted or
\r
203 alphabetical) then the sort function will need to be
\r
204 modified. Replacing (car saved-search) by (notmuch-saved-search-get
\r
205 saved-search :name) and (cdr saved-search) by
\r
206 (notmuch-saved-search-get saved-search :query) should be sufficient.
\r
208 The keys of `notmuch-tag-formats` are now regexps
\r
210 Previously, the keys were literal strings. Customized settings of
\r
211 `notmuch-tag-formats` will continue to work as before unless tags
\r
212 contain regexp special characters like `.` or `*`.
\r
214 Changed tags are now shown in the buffer
\r
216 Previously tag changes made in a buffer were shown immediately. In
\r
217 some cases (particularly automatic tag changes like marking read)
\r
218 this made it hard to see what had happened (e.g., whether the
\r
219 message had been unread).
\r
221 The changes are now shown explicitly in the buffer: by default
\r
222 deleted tags are displayed with red strike-through and added tags
\r
223 are displayed underlined in green (inverse video is used for deleted
\r
224 tags if the terminal does not support strike-through).
\r
226 The variables `notmuch-tag-deleted-formats` and
\r
227 `notmuch-tag-added-formats`, which have the same syntax as
\r
228 `notmuch-tag-formats`, allow this to be customized.
\r
230 Setting `notmuch-tag-deleted-formats` to `'((".*" nil))` and
\r
231 `notmuch-tag-added-formats` to `'((".*" tag))` will give the old
\r
232 behavior of hiding deleted tags and showing added tags identically
\r
233 to tags already present.
\r
237 The new, build-time generated variable `notmuch-emacs-version` is used
\r
238 to distinguish between notmuch cli and notmuch emacs versions.
\r
239 The function `notmuch-hello-versions` (bound to 'v' in notmuch-hello
\r
240 window) prints both notmuch cli and notmuch emacs versions in case
\r
241 these differ from each other.
\r
242 This is especially useful when using notmuch remotely.
\r
244 Ido-completing-read initialization in Emacs 23
\r
246 `ido-completing-read` in Emacs 23 versions 1 through 3 freezes unless
\r
247 it is initialized. Defadvice-based *Ido* initialization is defined
\r
248 for these Emacs versions.
\r
250 Bug fix for saved searches with newlines in them
\r
252 Split lines confuse `notmuch count --batch`, so we remove embedded
\r
253 newlines before calling notmuch count.
\r
255 Bug fixes for sender identities
\r
257 Previously, Emacs would rewrite some sender identities in unexpected
\r
258 and undesirable ways. Now it will use identities exactly as
\r
259 configured in `notmuch-identities`.
\r
261 Replies to encrypted messages will be encrypted by default
\r
263 In the interest of maintaining confidentiality of communications,
\r
264 the Notmuch Emacs interface now automatically adds the mml tag to
\r
265 encrypt replies to encrypted messages. This should make it less
\r
266 likely to accidentally reply to encrypted messages in plain text.
\r
268 Reply pushes mark before signature
\r
270 We push mark and set point on reply so that the user can easily cut
\r
271 the quoted text. The mark is now pushed before the signature, if
\r
272 any, instead of end of buffer so the signature is preserved.
\r
274 Message piping uses the originating buffer's working directory
\r
276 `notmuch-show-pipe-message` now uses the originating buffer's
\r
277 current default directory instead of that of the `*notmuch-pipe*`
\r
283 nmbug adds a `clone` command for setting up the initial repository and
\r
284 uses `@{upstream}` instead of `FETCH_HEAD` to track upstream changes.
\r
286 The `@{upstream}` change reduces ambiguity when fetching multiple
\r
287 branches, but requires existing users update their `NMBGIT`
\r
288 repository (usually `~/.nmbug`) to distinguish between local and
\r
289 remote-tracking branches. The easiest way to do this is:
\r
291 1. If you have any purely local commits (i.e. they aren't in the
\r
292 nmbug repository on nmbug.tethera.net), push them to a remote
\r
293 repository. We'll restore them from the backup in step 4.
\r
294 2. Remove your `NMBGIT` repository (e.g. `mv .nmbug .nmbug.bak`).
\r
295 3. Use the new `clone` command to create a fresh clone:
\r
297 nmbug clone http://nmbug.tethera.net/git/nmbug-tags.git
\r
299 4. If you had local commits in step 1, add a remote for that
\r
300 repository and fetch them into the new repository.
\r
304 Notmuch is a system for indexing, searching, reading, and tagging
\r
305 large collections of email messages in maildir or mh format. It uses
\r
306 the Xapian library to provide fast, full-text search with a convenient
\r
309 For more about notmuch, see http://notmuchmail.org
\r
313 Content-Type: application/pgp-signature
\r
315 -----BEGIN PGP SIGNATURE-----
\r
318 iQGcBAEBCAAGBQJTaJlfAAoJEPIClx2kp54sI3AL/02OOVzIHYO75gkk0IPNrzw0
\r
319 Tt6mzcMTzeyKuCtTKUvelL5gOXgUpDLZm0IjkKcX2j6azdTqlT1c1xK+6vAqEeOO
\r
320 T4ad61qUuGGodzkXtjKzsi+wiiIlxlRAUcIRYmMeRrIdL7Q28HTd58erTfM++mN6
\r
321 ft4go7RrAVpKbhhpNQ+WnQR0BVFLlp31OJxqCWo3SlujCiqWEMellYFbuqT08q1p
\r
322 NO2wn+3zDcbkzQ2ZWyIVtt2Ooyk8S/uho7Dy3cVqUqisaqc6/7h4U8DiaNMM49ci
\r
323 lgxEiAjrJrDbESh8vDQc/DMuIF+uFAVhL6svbJZyf9mvKehkx29YbhndGKHqKDWJ
\r
324 A8X3WmQc2u64fW5sgR9cvVes8faLhLA7ogr+z5hmatnUAbnK6Df8O4lHcBNo3V7R
\r
325 xrBuMXNswE7F/WSVHtMxi6vRpGFieE7oak6Y9IhbGkgPZx+ZsnaBqpbc55yHAo3W
\r
326 M0ZRwWpi+AnKWR/a2TdGz/siPnaP01hIR39oyePo+w==
\r
328 -----END PGP SIGNATURE-----
\r