Bug 273730 - with word wrap on, caret changes position within a word if line length is exceeded
Summary: with word wrap on, caret changes position within a word if line length is exc...
Status: RESOLVED DUPLICATE of bug 168534
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: 2.0.85
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 15:22 UTC by kadlecf
Modified: 2011-05-22 22:11 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kadlecf 2011-05-20 15:22:29 UTC
Version:           2.0.85 (using KDE 4.4.4) 
OS:                Linux

When editing text with soft word wrap enabled, there is a bug when text needs to be wrapped and the caret is within the last word of the line but not at its end. The word with the caret will be moved to the next line, but the caret will not conserve its position within the word. By the way, also the option "Show static word wrap marker" is checked.


Reproducible: Always

Steps to Reproduce:
Example, with word wrap enabled after 90 character. First let us write:

one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen

Then place the caret in the middle of the word fourteen and just type: 
"MY CAT ATE MY FISH". 

Actual Results:  
The result is:

one two three four five six seven eight nine ten eleven twelve thirteen fourMY CAT ATE
teenMY FISH fifteen

. Sometimes, the whole Kile will even crash soon after that; this occurred e.g. after pressing Ctrl-End to go to the end of file.

Expected Results:  
one two three four five six seven eight nine ten eleven twelve thirteen fourMY CAT ATE
MY FISHteen fifteen

OS: Linux (i686) release 2.6.34.7-0.5-pae
Compiler: gcc
Comment 1 Michel Ludwig 2011-05-22 22:11:09 UTC
Please update to KDE 4.5 (at least). This bug has been fixed there.

*** This bug has been marked as a duplicate of bug 168534 ***