Bug 315313 - Kmail: Hard line breaking turned on by default
Summary: Kmail: Hard line breaking turned on by default
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.9.4
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-17 09:52 UTC by Blue Glacier
Modified: 2017-01-07 22:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blue Glacier 2013-02-17 09:52:59 UTC
I noticed that by default, hard line breaking is activated. This makes
an
email harder to
read
espacially on low-resolution-screens
such
as cell phones, 
while on big screens, there
will 
be a huge empty space in the thight corner of the window, which is not appropriate. Do you know what I mean? It took some time to find out how to disable it. Finally, I made it, but what's the use of it? Maybe there are some who swear on it, but I guess for 90 percent of all users this is just annoying feature.

Reproducible: Always

Steps to Reproduce:
1. Do a fresh Installation of Kmail
2. Create a new Mail and write some text.
Actual Results:  
You will see that by default Kmail does a hard line break before the window ends.

Expected Results:  
The text should fill out the hole window and adapt itself dynamically to its size just directly after the Installation. Also, in the Options menu (of the composer?), you will find "Line Breaking" enabled by default. This is an unnecesscary handicap. It is easy to disable, but it is annoying.
Comment 1 Denis Kurz 2016-09-24 18:14:54 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 22:20:58 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.