Bug 167894

Summary: Composer: wrapping doesn't wrap
Product: [Unmaintained] knode Reporter: Darin McBride <Tanktalus>
Component: generalAssignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: daniel.moyne, gdamjan, greatbunzinni, nive, spatz
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Darin McBride 2008-07-31 21:33:29 UTC 
Version:           0.99.01 (using KDE 4.1.0)
Installed from:    Gentoo Packages
Compiler:          gcc version 4.1.2 (Gentoo 4.1.2 p1.1)
 Target: x86_64-pc-linux-gnu
OS:                Linux

After writing a lengthy reply to a usenet post, knode complained that some of my lines were >80 characters with its full warning about poor netiquette.  This confused me, as I used to get this in kde3.5 only when I pasted long URLs, and I knew I hadn't.  So I went back, checked every line for where it might have gone over 80 characters, and couldn't find one over 77 characters.  So I ignored the warning.

Then, I went back to read what got posted.  And, apparently, the warning was right: no wordwrapping occurred, regardless of what it looked like in my composer screen.
Comment 1 gdamjan 2008-09-18 18:13:30 UTC 
The same thing happens to me too... Knode wraps the text in the editor, but when sent the text is not wrapped.. It looks suspiciously similar to the soft-wrap option in kwrite and other editors.

The worst part is, you need to wrap the lines BY HAND then... ugly.

This is on:
KNode Version 0.99.01
Using KDE 4.1.1 (KDE 4.1.1)
Comment 2 Darin McBride 2008-10-24 19:44:07 UTC 
Still happening in kde 4.1.70
Comment 3 greatbunzinni 2008-11-16 11:48:01 UTC 
This bug is still present in knode 0.99.01 from KDE 4.1.2, kubuntu 8.10.
Comment 4 Olivier Trichet 2008-12-09 12:57:44 UTC 

*** This bug has been marked as a duplicate of bug 167996 ***
Comment 5 Olivier Trichet 2009-01-18 01:51:23 UTC 
*** Bug 179792 has been marked as a duplicate of this bug. ***