1 Return-Path: <jrollins@finestructure.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 42BDA431FB6
\r
6 for <notmuch@notmuchmail.org>; Tue, 15 May 2012 09:26:55 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled
\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 QhhuzCvdjveB for <notmuch@notmuchmail.org>;
\r
16 Tue, 15 May 2012 09:26:54 -0700 (PDT)
\r
17 Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu
\r
19 by olra.theworths.org (Postfix) with ESMTP id AC87F431FAE
\r
20 for <notmuch@notmuchmail.org>; Tue, 15 May 2012 09:26:54 -0700 (PDT)
\r
21 Received: from earth-doxen.imss.caltech.edu (localhost [127.0.0.1])
\r
22 by earth-doxen-postvirus (Postfix) with ESMTP id 4AB2266E0167
\r
23 for <notmuch@notmuchmail.org>; Tue, 15 May 2012 09:26:52 -0700 (PDT)
\r
24 X-Spam-Scanned: at Caltech-IMSS on earth-doxen by amavisd-new
\r
25 Received: from finestructure.net (lair.fifthhorseman.net [108.58.6.98])
\r
26 (Authenticated sender: jrollins)
\r
27 by earth-doxen-submit (Postfix) with ESMTP id A299A66E00E5
\r
28 for <notmuch@notmuchmail.org>; Tue, 15 May 2012 09:26:43 -0700 (PDT)
\r
29 Received: by finestructure.net (Postfix, from userid 1000)
\r
30 id 6050B995; Tue, 15 May 2012 09:26:42 -0700 (PDT)
\r
31 From: Jameson Graef Rollins <jrollins@finestructure.net>
\r
32 To: Notmuch Mail <notmuch@notmuchmail.org>
\r
33 Subject: [PATCH] add NEWS item about new emacs tagging interface.
\r
34 Date: Tue, 15 May 2012 09:26:42 -0700
\r
35 Message-Id: <1337099202-4609-1-git-send-email-jrollins@finestructure.net>
\r
36 X-Mailer: git-send-email 1.7.10
\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, 15 May 2012 16:26:55 -0000
\r
51 This is fairly important to mention, since it represents a user
\r
54 Sorry about it being late!
\r
56 NEWS | 14 +++++++++++++-
\r
57 1 file changed, 13 insertions(+), 1 deletion(-)
\r
59 diff --git a/NEWS b/NEWS
\r
60 index f987811..69a7203 100644
\r
63 @@ -15,7 +15,7 @@ JSON reply format
\r
65 "notmuch reply" can now produce JSON output that contains the headers
\r
66 for a reply message and full information about the original message
\r
67 - begin replied to. This allows MUAs to create replies intelligtently.
\r
68 + begin replied to. This allows MUAs to create replies intelligently.
\r
69 For example, an MUA that can parse HTML might quote HTML parts.
\r
71 Calling notmuch reply with --format=json imposes the restriction that
\r
72 @@ -60,6 +60,18 @@ Listing configuration items
\r
76 +Changes to tagging interface
\r
78 + The user-facing tagging functions in the Emacs interface have been
\r
79 + normalized across all notmuch modes. The tagging functions are now
\r
80 + 'notmuch-search-tag' in search-mode, and 'notmuch-show-tag' in
\r
81 + show-mode. They accept a string representing a single tag change,
\r
82 + or a list of tag changes. See 'M-x describe-function notmuch-tag'
\r
83 + for more information.
\r
85 + NOTE: This breaks compatibility with old tagging functions, so user
\r
86 + may need to update in custom configurations.
\r
88 Reply improvement using the JSON format
\r
90 Emacs now uses the JSON reply format to create replies. It obeys
\r