GNOME Bugzilla – Bug 781178
line breaks lost when selecting and replying to certain messages
Last modified: 2017-12-02 01:39:46 UTC
First reported here: https://mail.gnome.org/archives/geary-list/2017-March/msg00001.html As I had no feedback, I'm reporting it here as well. Steps to reproduce: - select part of a message where you have a line break - reply using either a keyboard shortcut or the menu - RESULT: line break removed in the quoted text NOTE: I've just realized that it does not occur always. So it might depend on the quoted message. It seems it always happens when I reply to my own messages. Behaviour with other messages changes. Here's some header information of a message which I can select and reply to correctly: Content-Type: multipart/alternative; boundary=001a113ebccc09d262054c832638 --001a113ebccc09d262054c832638 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable And this is the header of a message where I get no line breaks if I select and reply: Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Probably not much helpful.. Let me know how can I provide better information.
Yep, I've seen it as well, it's is pretty annoying.
I'm checking again... It seems that quoted text is not correct when replying to a text only message. The default mode of Geary composer, plain text or HTML, is not relevant. What matters is the message you are replying to. Mike, I've just made a test on an email sent by you, which had just these: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable and quoted text appears compressed in a single paragraph. Quoted text appears correct when the messages are a mix of HTML and plain text. For example, I've just made a test on a message sent by Yahoo mail, which is set up this way: Content-Type: multipart/alternative; boundary="----=_Part_6368312_1754565969.1508965255048" ------=_Part_6368312_1754565969.1508965255048 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [here's the plain text] ------=_Part_6368312_1754565969.1508965255048 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <html><head></head><body> [here's the HTML]
So it looks like '\n' is removed in selected text quoted in the reply (while '<br>' is kept).
Fix for this and a followup pushed to master as commit c2afe8f and commit 1d746e4. Will bake for a while the cherry pick onto geary-0.12.
Great! I confirm it works fine again!
Cherry picked to geary-0.12 as commit db41c30 and commit 0fdbe5d, resolving as fixed.