(In reply to Jorg K (GMT+1) from comment #43)
> Created attachment 8693516
> Unbitrotted patch.
>
> I found this bug looking for "patchlove". I refreshed the patch.
>
> This is the result:
> from: =?UTF-8?Q?J=c3=b6rg_Knobloch?= <email address hidden>
> subject: some subject
> to: <email address hidden>
>
> Pretty ugly:
> - The headers need to be RFC 2047 decoded.
> - lowercase in the field names.
That sounds doable?
> So the question is, before I invest more work here: Does anyone want this?
Definitely yes. 17 votes, 8 duplicates across many years. And it's just a freaking annoyance if any relevant text content which is right in front of me cannot be copied and reused for other purposes. Email addresses clearly qualify as relevant text content. Subject is already copyable.
> The nice add-on "HeaderToolsLite" also gives access to the headers, you can
> even edit them.
Thanks for the pointer. Ability to copy relevant text content should be core functionality.
(In reply to Jorg K (GMT+1) from comment #43) Q?J=c3= b6rg_Knobloch? = <email address hidden>
> Created attachment 8693516
> Unbitrotted patch.
>
> I found this bug looking for "patchlove". I refreshed the patch.
>
> This is the result:
> from: =?UTF-8?
> subject: some subject
> to: <email address hidden>
>
> Pretty ugly:
> - The headers need to be RFC 2047 decoded.
> - lowercase in the field names.
That sounds doable?
> So the question is, before I invest more work here: Does anyone want this?
Definitely yes. 17 votes, 8 duplicates across many years. And it's just a freaking annoyance if any relevant text content which is right in front of me cannot be copied and reused for other purposes. Email addresses clearly qualify as relevant text content. Subject is already copyable.
> The nice add-on "HeaderToolsLite" also gives access to the headers, you can
> even edit them.
Thanks for the pointer. Ability to copy relevant text content should be core functionality.