Bug 64382 (suse49382) - KMail: Automatic line wrapping doesn't work correctly with tabs
Summary: KMail: Automatic line wrapping doesn't work correctly with tabs
Status: RESOLVED WONTFIX
Alias: suse49382
Product: openSUSE 10.2
Classification: openSUSE
Component: KDE (show other bugs)
Version: Final
Hardware: All Linux
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Will Stephenson
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-18 00:14 UTC by Ralf Haferkamp
Modified: 2007-05-14 14:36 UTC (History)
3 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Haferkamp 2004-12-18 00:14:29 UTC
My KMail is configured to wrap lines after at the 78th column. But when I start
a line with a Tab it seems to count the Tab only as one character (instead of 8)
and the line is wrapped after 86 characters. 
(Funny enough in the status bar where the actual column is displayed a Tab
character seems to be counted correctly).
Comment 1 Ralf Haferkamp 2004-12-18 00:14:29 UTC
<!-- SBZ_reproduce  -->
Start KMail, set automatic line wrapping to wrap after 78 columns, enter a line
that starts with a tab, continue to type in words as long as the line is wrapped.
Comment 2 Christian Boltz 2005-03-19 23:10:30 UTC
Bug still exists in 9.3 beta3 - updating product and version. 
Comment 3 Christian Boltz 2005-12-22 21:59:16 UTC
I just reproduced the problem with KDE 3.5 (KMail 1.9.1) from supplementary on SUSE 10.0.

Since this KDE version is also used in current alpha, I will set product and version to 10.1 alpha - I guess the bug is also present there.
Comment 4 Christian Boltz 2007-01-03 00:09:18 UTC
I missed the second birthday of this bug ;-) so I'll wish a happy new year instead *g*

(read: still reproducable in 10.2 final)
Comment 5 Will Stephenson 2007-05-14 14:36:03 UTC
Reflecting reality, please track this bug upstream - I'm not going to fix it :(.

http://bugs.kde.org/show_bug.cgi?id=64537