Open Bug 1845259 Opened 3 years ago Updated 3 years ago

No way to send a patch or text with tabs/spaces in a verbatim text format

Categories

(Thunderbird :: Message Compose Window, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: trailman, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:109.0) Gecko/20100101 Firefox/113.0

Steps to reproduce:

Installed Thunderbird 115 on Linux using a fresh new profile
Tried to send a patch (for Linux kernel development) in text mode. I found that the only way to have tabs sent correctly was to paste the patch in the composer window previously set to Paragraph="Preformat". And In options I selected delivery as text only for this email.

Note : same issue with older versions : 68 and 78 tested on Linux (32 and 64bit OS)

Actual results:

The patch looks good in the composer window (spaces and tabs are correct), BUT once the email has been sent, I see that an extra space has been added at the beginning of each line starting with a space (confirmed by dumping the "Sent" file in the ~/.thunderbird/... profile). So the patch is declared invalid by the recipient.

Expected results:

I expected to have thunderbird send a verbatim copy of my patch, or at least a way to configure something to do so.

NOTE : it seems this issue has already been reported and marked invalid because this is inherent to format=flowed (see bugzilla #391765 or #608514), but nobody answered how to do without format=flowed or gave a workaround/setting to avoid this. So still no solution to send some text "as is" in a verbatim way.

Workaround :
In addition to select "Preformat" in composer window before pasting the text, also select "text only" as option for delivery format, it is also required to have flowed format disabled :
Edit / Parameters / General / Config Editor , then search for "flowed", then double click on "mailnews.send_plaintext_flowed" to set it to "false".
But this is NOT easy to do and must be reverted back (really ?) to "true" once email has been sent.

You need to log in before you can comment on or make changes to this bug.