Re: [BUG] Custom headers in `notmuch-message-headers` are broken

Subject:Re: [BUG] Custom headers in `notmuch-message-headers` are broken

Date:Thu, 26 Jul 2018 14:55:39 +0800

To:Jan Malakhovski ,Amin Bandali

Cc:notmuch@notmuchmail.org

From:David Bremner


Jan Malakhovski <oxij@oxij.org> writes:

>> 3) We should think carefully about whether we want to blindly send
>>    certain large headers like "Received". Some people use notmuch via
>>    ssh or equivalent, and it might (dunno) be a concern.
>
> I'd prefer `notmuch show` to dump everything by default and have an
> option like `--headers` to limit those. I.e. to get current behavior
> you'd just dump comma-separated `notmuch-message-headers` into that
> option in `notmuch.el` and be happy.

that would be an option, it would require updating the elisp.

>
>> 1) You'll want to avoid duplicating headers already emitted
>
> Why? Wouldn't that prevent you from parsing "Received" headers in
> `notmuch.el`?

I just meant that the code has already emitted e.g. "Cc" by the time it
reaches the block Amin points to.

_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Thread: