Moving cursor vertically with dynamic word wrap

Bug #373610 reported by Luca Citi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Software Development Kit
Won't Fix
Wishlist
kdesdk (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

Binary package hint: kate

Hi!
This bug (or at least unexpected behaviour) applies to kile (1:2.1.0~svn942443-0ubuntu4), kate (4:4.2.2-0ubuntu1), ...
I am using Kubuntu 9.04.
Here is what happens:
- I have an indentated text with lines long more than the text area width that are dynamically word wrapped (see figure)
- I start with the cursor in position line=1 col=1
- I move the down arrow repeatedly
- The cursor moves through the following positions: (1,1) -> (2,1) -> (3,1) -> (4,1) -> (4,74) -> (5,5) -> (6,5)
What I expected (and find useful) is that the cursor should go back to column 1 as soon as it is "available" again,
i.e.: (1,1) -> (2,1) -> (3,1) -> (4,1) -> (4,74) -> (5,1) -> (6,1).
The current behaviour makes simple operations, e.g. the selection of blocks of source code, more difficult.
Thanks,
Luca

Revision history for this message
Luca Citi (knulp79) wrote :
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Thank you for filing this bug report. I can confirm this - going down from an unindented line to an indented line to an unindented line gets me to col 5 instead of 1.

Changed in kdesdk (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
Changed in kdesdk:
status: Unknown → Confirmed
Revision history for this message
In , Yuriy Kozlov (yuriy-kozlov) wrote :

Version: (using KDE 4.2.2)
Installed from: Ubuntu Packages

This bug (or at least unexpected behaviour) applies to kile (1:2.1.0~svn942443-0ubuntu4), kate (4:4.2.2-0ubuntu1), ...
I am using Kubuntu 9.04.
Here is what happens:
 - I have an indentated text with lines long more than the text area width that are dynamically word wrapped (see figure)
 - I start with the cursor in position line=1 col=1
 - I move the down arrow repeatedly
 - The cursor moves through the following positions: (1,1) -> (2,1) -> (3,1) -> (4,1) -> (4,74) -> (5,5) -> (6,5)
What I expected (and find useful) is that the cursor should go back to column 1 as soon as it is "available" again,
 i.e.: (1,1) -> (2,1) -> (3,1) -> (4,1) -> (4,74) -> (5,1) -> (6,1).

In other words, going down from from col 1 on an unindented line to an indented line to an unindented line gets me to col 5 instead of 1.

The current behavior makes simple operations, e.g. the selection of blocks of source code, more difficult.

Revision history for this message
In , Yuriy Kozlov (yuriy-kozlov) wrote :
Changed in kdesdk (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Luca Citi (knulp79) wrote :

Dear Yuriy,
thank you for taking care of this report.
I would not put it in a wishlist.
It is a bug, it is annoying.
Not a severe bug, but still a bug.
No other editor (nor previous versions of kate) works like this.
Bye,
Luca

Changed in kdesdk:
importance: Unknown → Wishlist
Revision history for this message
In , Cullmann-t (cullmann-t) wrote :

Dear user,

this wish list item is now closed, as it wasn't touched in the last two years and no contributor stepped up to implement it.

The Kate/KTextEditor team is very small and we can just try to keep up with fixing bugs. Therefore wishs that show no activity for two years or more will be closed from now on to keep at least a bit overview about 'current' wishs of the users.

If you want your feature to be implemented, please step up to provide some patch for it. If you think it is really needed, you can reopen your request, but keep in mind, if no new good arguments are made and no people get attracted to help out to implement it, it will expire in two years again.

We have a nice website kate-editor.org that provides all the information needed to contribute, please make use of it. For highlighting improvements our user manual shows how to write syntax definition files.

Greetings
Christoph

Changed in kdesdk:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.