From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Cc: tomi.ollila@iki.fi
Subject: Re: [PATCH V2 1/1] NEWS: under-the-hood Emacs interface fixes
Date: Sat, 08 Dec 2012 15:28:35 -0400 [thread overview]
Message-ID: <87hanwqr6k.fsf@zancas.localnet> (raw)
In-Reply-To: <1354920773-27654-1-git-send-email-tomi.ollila@iki.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> Added the following Emacs Interface NEWS entries:
>
> Catch errors bodypart insertions may throw,
> Improved text/calendar content handling and
> Disabled coding conversions when reading in
> `with-current-notmuch-show-message`.
>
Some suggestions about wording:
diff --git a/NEWS b/NEWS
index 6970178..2e1c054 100644
--- a/NEWS
+++ b/NEWS
@@ -28,7 +28,7 @@ Removal of the deprecated `notmuch-folders` variable
has now been removed. Any remaining users should migrate to
`notmuch-saved-searches`.
-Handle errors bodypart insertions may throw
+Handle errors from bodypart insertions
If displaying the text of a message in show mode causes an error (in
the `notmuch-show-insert-part-*` functions), notmuch no longer cuts
@@ -38,9 +38,9 @@ Handle errors bodypart insertions may throw
Improved text/calendar content handling
Carriage returns in embedded text/calendar content caused insertion
- of calendar content fail. Now CRs are removed before calling icalendar
+ of the calendar content fail. Now CRs are removed before calling icalendar
to extract icalendar data. In case icalendar extraction fails an error
- is thrown for bodypart insertion function to react upon it.
+ is thrown for the bodypart insertion function to deal with.
Disabled coding conversions when reading in `with-current-notmuch-show-message`
prev parent reply other threads:[~2012-12-08 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 22:52 [PATCH V2 1/1] NEWS: under-the-hood Emacs interface fixes Tomi Ollila
2012-12-08 19:28 ` David Bremner [this message]
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=87hanwqr6k.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).