From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Cc: notmuch@freelists.org, Tomi Ollila <tomi.ollila@iki.fi>
Subject: [PATCH] NEWS for release 0.25: Emacs: support for stashing message timestamp
Date: Sun, 23 Jul 2017 22:38:14 +0300 [thread overview]
Message-ID: <20170723193814.13952-1-tomi.ollila@iki.fi> (raw)
---
NEWS | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/NEWS b/NEWS
index f844f1a77d93..4f3bdfa5752b 100644
--- a/NEWS
+++ b/NEWS
@@ -8,7 +8,7 @@ Add regexp searching for mid, paths, and tags.
Skip HTML tags when indexing
- In particular this avoids indexing large inline images.
+ In particular this avoids indexing large inline images.
Command Line Interface
----------------------
@@ -20,6 +20,12 @@ Allow space as separator for keyword arguments.
Emacs
-----
+Support for stashing message timestamp in show and tree views
+
+ Invoking `notmuch-show-stash-date` with a prefix argument
+ stashes the unix timestamp of the current message instead of
+ the date string.
+
Don't use 'function' as variable name, workaround emacs bug 26406.
Library Changes
@@ -27,14 +33,14 @@ Library Changes
Add workaround for date parsing of bad input in older GMime
- In certain circumstances, older GMime libraries could return
- negative numbers when parsing syntactically invalid dates.
+ In certain circumstances, older GMime libraries could return
+ negative numbers when parsing syntactically invalid dates.
Replace deprecated functions with status returning versions
- API of notmuch_query_{search,count}_{messages,threads} has
- changed. notmuch_query_add_tag_exclude now returns a status
- value.
+ API of notmuch_query_{search,count}_{messages,threads} has
+ changed. notmuch_query_add_tag_exclude now returns a status
+ value.
Add support for building against GMime 3.0.
--
2.12.2
reply other threads:[~2017-07-24 0:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170723193814.13952-1-tomi.ollila@iki.fi \
--to=tomi.ollila@iki.fi \
--cc=notmuch@freelists.org \
--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).