subjects and duplicated message id's

David Bremner david at tethera.net
Thu Dec 14 17:23:23 PST 2017


>>    - we could also force the value slot to have the lexico first files'
>>      subject during indexing. This would be a bit fiddly, but localized.
>>      It would have the surprising effect of having the subject updated
>>      when new messages arrived.
>
> This is a bit weird, unless we also force "notmuch show" to always show
> the lexicographically-first file as well, no?

AFAIU, this is the current behaviour, see the second test in T670-duplicate-mid.

> Obviously, i'd prefer the original subject, so that it's searchable.
> I'd also like it if "notmuch show" displayed the original subject when
> showing the encrypted message.
>
> However, if someone does "notmuch show --decrypt=false" i'd want it to
> display the as-delivered header.
>
> Does this help push you toward any specific decision?  I'm also not sure
> what the correct solution is right now.

I don't think it really pushes one way or the other. The --decrypt=false
case could just look at the file instead of the database (that's what
notmuch-show does now.



More information about the notmuch mailing list