Justus Winter writes:
> I think I found a reproducer:
>
> mkdir -p /tmp/selection-bug/{tmp,new,cur}
> echo "[database]
> path=/tmp/selection-bug" > /tmp/selection-bug/notmuch-config
> NOTMUCH_CONFIG=/tmp/selection-bug/notmuch-config notmuch new
> NOTMUCH_CONFIG=/tmp/selection-bug/notmuch-config
* Thibault Polge , 2022-09-21 16:15:
Subject: =?UTF-8?B?TGl2cmFpc29uIHByw6l2dWUgcG91ciBhdWpvdXJk4oCZaHU=?=
=?UTF-8?B?aTogUkVTVFJBUCBTYWRkbGUgQmFnIFNhY2NvY2hlLi4u?=
Notmuch displays the subject as only the decoded contents of the first
fragment
I believe this is now fixed in GMime upstream:
Attaching the reprocucer scripts, which somehow got lost in transport!?
--
Jakub Wilk
#!/bin/bash
set -e -u
tmpdir="$(mktemp -d)"
export NOTMUCH_DATABASE="$tmpdir"
notmuch --config '' new > /dev/null
mkdir -p "$NOTMUCH_DATABASE"/{cur,new,tmp}
notmuch --config '' insert > /dev/null
notmuch
Package: notmuch
Version: 0.37-1
The attached message has a bunch of RFC-2047-encoded special characters
in the display-name part of the From field:
$ grep ^From: weird-from.eml
From: =?UTF-8?Q?=3Cfoo=40example.org=3E=2C?=
When you show this message in notmuch, the special characters
On Wed, Oct 12 2022, Robin Jarry wrote:
> Hi Tomi,
>
> Tomi Ollila, Oct 12, 2022 at 21:39:
>> > diff --git a/notmuch-show.c b/notmuch-show.c
>> > index ee9efa7448d7..ad31e0123268 100644
>> > --- a/notmuch-show.c
>> > +++ b/notmuch-show.c
>> > @@ -1159,6 +1159,18 @@ do_show_threaded (void *ctx,
>>
Jakub Wilk writes:
> * David Bremner , 2022-10-11 08:20:
>>>This is completely untested, but hey, what could possibly go wrong?
>>
>>I've yolo-ed this into production on nmbug.notmuchmail.org. Maybe you
>>can poke at it and see if it looks like you expect.
>
> Looks good. Thanks!
>
applied to
