From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: [PATCH] add NEWS item about new emacs tagging interface.
Date: Tue, 15 May 2012 09:26:42 -0700 [thread overview]
Message-ID: <1337099202-4609-1-git-send-email-jrollins@finestructure.net> (raw)
This is fairly important to mention, since it represents a user
interface change.
---
Sorry about it being late!
NEWS | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index f987811..69a7203 100644
--- a/NEWS
+++ b/NEWS
@@ -15,7 +15,7 @@ JSON reply format
"notmuch reply" can now produce JSON output that contains the headers
for a reply message and full information about the original message
- begin replied to. This allows MUAs to create replies intelligtently.
+ begin replied to. This allows MUAs to create replies intelligently.
For example, an MUA that can parse HTML might quote HTML parts.
Calling notmuch reply with --format=json imposes the restriction that
@@ -60,6 +60,18 @@ Listing configuration items
Emacs Interface
---------------
+Changes to tagging interface
+
+ The user-facing tagging functions in the Emacs interface have been
+ normalized across all notmuch modes. The tagging functions are now
+ 'notmuch-search-tag' in search-mode, and 'notmuch-show-tag' in
+ show-mode. They accept a string representing a single tag change,
+ or a list of tag changes. See 'M-x describe-function notmuch-tag'
+ for more information.
+
+ NOTE: This breaks compatibility with old tagging functions, so user
+ may need to update in custom configurations.
+
Reply improvement using the JSON format
Emacs now uses the JSON reply format to create replies. It obeys
--
1.7.10
next reply other threads:[~2012-05-15 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 16:26 Jameson Graef Rollins [this message]
2012-05-16 0:19 ` [PATCH] add NEWS item about new emacs tagging interface David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1337099202-4609-1-git-send-email-jrollins@finestructure.net \
--to=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).