After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 647947 - Automated line breaks bugs when replying to some messages
Automated line breaks bugs when replying to some messages
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Composer
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Tomas Popela
Evolution QA team
evolution[composer] evolution[webkit]
Depends on:
Blocks:
 
 
Reported: 2011-04-16 15:40 UTC by Milan Bouchet-Valat
Modified: 2021-05-19 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Bouchet-Valat 2011-04-16 15:40:06 UTC
When I reply to a message that includes lines longer than the automated line break size, the automated breaks work when writing after the quoted text, but not when writing in the middle of it.

Illustration (Bugzilla will probably insert line breaks too, but you understand what I mean):

On Saturday, April 16th You wrote:
> Some long text line that exceeds the maximum length, really really long you see
> [Writing text here after removing the opening > doesn't break correctly.]
> Another line that exceeds the maximum length, really really long you see
[Writing text here breaks correctly.]


But probably the original bug is that the message I'm replying to misses the line breaks in Evo in the first place. It's a plain text message that *has* correct line breaks in the source, but for some reason they are removed from the preview and the reply.

The source of the message looks correct:
Start of the long sentence blah blah truncated=[U+000D]
and continues on another line...[U+000D]

FWIW, it was send using iPhone Mail (8F190).

Please ask if I can be more helpful, I find it hard to explain these line breaks issues... I'm using Evolution 3.1.0.
Comment 1 Matthew Barnes 2011-04-16 16:12:04 UTC
Pay attention to the paragraph mode, indicated on the editing toolbar.  Blocks of text with really long lines are mostly likely in "Preformatted" paragraph mode, which does not line wrap automatically.

When you start typing after the quoted text, the composer should be in "Normal" paragraph mode, which *does* line wrap automatically.

When you start typing in the middle of a block of text in "Preformatted" paragraph mode, the composer is probably remaining in that mode, and you'll have to switch back to "Normal" paragraph mode manually (or highlight what you've already typed and then switch modes).
Comment 2 Milan Bouchet-Valat 2011-04-16 16:48:04 UTC
Right, thanks for the tip! Though I still believe there are two bugs:
1) The message should have correct line breaks in the first place since they are present in the source.

2) The Preformatted thing is confusing: maybe if you remove the initial > from an empty quoted line, it should go back to Normal. It's not unusual you remove an empty line from a quoted message to reply just below some text. In that case, people cannot understand why writing would work differently than in other places.

(Maybe I can open another bug for 1) if that helps.)
Comment 3 Milan Bouchet-Valat 2011-05-20 07:55:13 UTC
See bug 650645 for 1. Let's say this report is for 2), unless you think my suggestion is silly. ;-)
Comment 4 alski85 2015-04-27 17:03:40 UTC
This bug affects me as well.  When using outlook style replies, the composer is set to 'HTML: Preformatted' for html messages.  If I start typing at the top, I'd expect it to be set to Normal, as typing at the top is the outlook style of replying.

In settings, I have Reply style set to 'Inline (Outlook style)', and 'Start typing at the bottom on replying' is unchecked.
Comment 5 André Klapper 2021-05-19 12:28:10 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.