Bug 325351 - Composer wraps unconditionally
Summary: Composer wraps unconditionally
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composereditor-ng (other bugs)
Version First Reported In: 4.10.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Laurent Montel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-27 02:22 UTC by Volker Kuhlmann
Modified: 2017-01-07 21:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Kuhlmann 2013-09-27 02:22:56 UTC
The wrap function in the composer is useful/essential for these situations:
* Typing new text.
* Quoted text in a reply, where whole paragraphs or more are on a single line.

It is seriously in the way in these:
* Typing or pasting URLs longer than the wrap margin.
* Quoted URLs in a reply.
* Explicitly trying to create new text with some lines exceeding the wrap margin.
This kind of thing leads to the kind of braindead emails with broken URLs many email clients seem to be incapable of preventing.

I personally view this as a bug that prevents serious use of the composer editor, not an enhancement request.

Reproducible: Always

Steps to Reproduce:
1. Enable wrap at 72
2a. Compose new email, paste a URL longer than 72 characters.
2b. Reply to an email containing a line with a URL longer than 72 characters.
Actual Results:  
URL is destroyed by wrapping.

Expected Results:  
URL is left intact.

Possibility to explicitly create lines longer than the wrap margin when typing new text.
Comment 1 Denis Kurz 2016-09-24 17:59:36 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:31:25 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.