Bug 249649 - Cursor in kate sometimes stays in place and characters are added on its right
Summary: Cursor in kate sometimes stays in place and characters are added on its right
Status: RESOLVED DUPLICATE of bug 246162
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-31 18:18 UTC by Nicolas Bigaouette
Modified: 2010-09-20 14:23 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Bigaouette 2010-08-31 18:18:15 UTC 
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

Sometimes while coding, the cursor will "freeze" in place and all characters typed will be added to the right of the cursor, leading to reverse/backward words.
When kate starts doing this, the only way to fix it is to to refresh the document pressing F5 (or closing kate obviously).

Reproducible: Sometimes

Steps to Reproduce:
It seems this happens randomly... I cannot find the right pattern. It occurs once every two days with heavy kate usage.

Actual Results:  
For example, typing "example" would lead to "elpmaxe" with the cursor still at the begining (left) of word.


Using KDE 4.4.5 on ArchLinux, Kate 3.4.5
Comment 1 Magnus Johansson 2010-09-20 12:37:27 UTC 
This just happened to me as well. KDE 4.4.5 on Gentoo, Kile 2.0.85, Kate Part 3.4.
Comment 2 Marco Mentasti 2010-09-20 13:57:48 UTC 
Same for me, on Debian unstable with KDE 4.4.5 / Kate 3.4.5, and on Windows XP with KDE 4.4.4 / Kate 3.4.4.
I can confirm that seems to happens randomly and rarely, after pressing Enter (the cursor remains at the same horizontal position of the previous line, but one line down)..
Might be a duplicate of #246162 ??
Comment 3 Milian Wolff 2010-09-20 14:23:18 UTC 

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