From: Mark Walters <markwalters1009@gmail.com>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH v2] Emacs related NEWS for 0.22.
In-Reply-To: <1460929193-31367-1-git-send-email-dme@dme.org>
References: <1460929193-31367-1-git-send-email-dme@dme.org>
User-Agent: Notmuch/0.21+17~g6d0b613 (http://notmuchmail.org) Emacs/24.4.1
 (x86_64-pc-linux-gnu)
Date: Sun, 17 Apr 2016 10:10:04 +0100
Message-ID: <87h9f0fvo3.fsf@qmul.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

On Sun, 17 Apr 2016, David Edmondson <dme@dme.org> wrote:
> ---
>  NEWS | 28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
>
> - Updated based on comments from Mark and re-reading.
>
> diff --git a/NEWS b/NEWS
> index 78d4708..cabcc1e 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -18,6 +18,34 @@ Filtering or Limiting messages is now bound to `l` in the search view
>  
>    This binding now matches the analogous binding in show view.
>  
> +`F` forwards all open messages in a thread
> +
> +  When viewing a thread of messages, the new binding `F` can be used
> +  to generate a new outgoing message which forwards all of the open
> +  messages in the thread. This is analogous to the `f` binding, which
> +  forwards only the current message.
> +
> +Preferred content type can be determined from the message content
> +
> +  More flexibility in choosing which sub-part of a
> +  multipart/alternative part is initially shown is available by
> +  setting `notmuch-multipart/alternative-discouraged` to a function
> +  that returns a list of discouraged types. The function so specified
> +  is passed the message as an argument and can examine the message
> +  content to determine which content types should be discouraged. This
> +  is in addition to the current capabilities (i.e. setting
> +  `notmuch-multipart/alternative-discouraged` to a list of discouraged
> +  types).
> +
> +When viewing a thread ("show" mode), queries that match no messages no
> +longer generate empty buffers
> +
> +  Should an attempt be made to view the thread corresponding to a
> +  query that matches no messages, a warning message is now displayed
> +  and the terminal bell rung rather than displaying an empty buffer
> +  (or, in some cases, displaying an empty buffer and throwing an
> +  error). This also affects re-display of the current thread.
> +

LGTM +1 (and thanks for clarifying it)

Best wishes

Mark


>  Documentation
>  -------------
>  
> -- 
> 2.1.4
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch