Re: Thunderbird and patches oddity (was: [PATCH] w32: Improve foreground window activation.)

Todd Zullinger via Gnupg-devel <[email protected]> Fri, 3 Jul 2026 10:13:41 -0400
Newsgroups gmane.comp.encryption.gpg.devel
Message-ID <[email protected]>
--===============2488057789615795272==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="HDyowf3wvszEzcyC"
Content-Disposition: inline

--HDyowf3wvszEzcyC
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Werner Koch via Gnupg-devel wrote:
> On Thu,  2 Jul 2026 20:33, Jacob Bachmeyer said:
>=20
>> I *think* that Thunderbird behaves differently if the text is
>> in a "Preformat" block.  This is an example.  I typed it in
>> "Preformat" style and broke the lines manually.
>=20
> I am not sure what a preformat block is in Thunderbird but assume that
> is related to HTML to Text conversion.  The patch mail had no HTML part
> but it was
>=20
> Content-Type: text/plain; charset=3DUTF-8; format=3Dflowed
>=20
> Your mail was also flawed^Wflowed.  But indeed the above quote paragraph
> was oka but your first paragraph had 0xC2, 0xA0, 0x20 sequences after
> the end of sentence fullstop.  And my quoted text was another part as
> text/html.
>=20
>> When pasting patches or other pre-formatted text into Thunderbird, I
>> have developed the habit of (1) starting a new paragraph, (2) changing
>> the style for that paragraph to "Preformat", (3) typing the "8<------"
>> lines, then (4) pasting the text between the scissor lines.
>=20
> Good advise.  But TB should stop this weird behaviour in particular if
> it is configured to send text/plain. =20

Perhaps the suggestions from the Git and Linux kernel
projects would be useful?

https://git-scm.com/docs/git-format-patch#_thunderbird
https://www.kernel.org/doc/html/latest/process/email-clients.html#thunderbi=
rd-gui

They include largely similar advice.  Alternately, the git
send-email=B9 command can be very helpful in removing the need
to fight with a mail client.  There is also the b4=B2 tool
which is used by the kernel folks and has recently been
proposed as the recommended method for the Git project as
well.

=B9 https://git-scm.com/docs/git-send-email
=B2 https://b4.docs.kernel.org/

--=20
Todd

--HDyowf3wvszEzcyC
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSvlwC4tRNlCF6x+moHOcdGE+n45gUCakfDigAKCRAHOcdGE+n4
5nBUAP9YtIvL49gZQDaGH7KILphOHPWZvmn6+Z5NB3iPjMTEYwD/by6wW2TnVbfv
PVUaz0fitDp8lk92iYiZECRLfYb40Qo=
=TZxF
-----END PGP SIGNATURE-----

--HDyowf3wvszEzcyC--


--===============2488057789615795272==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

--===============2488057789615795272==--