After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 421953 - Ctrl+left-arrow behaves inconsistantly with non-alphanumeric chars
Ctrl+left-arrow behaves inconsistantly with non-alphanumeric chars
Status: RESOLVED DUPLICATE of bug 727972
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-03-23 16:44 UTC by Sven Arvidsson
Modified: 2014-04-10 15:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sven Arvidsson 2007-03-23 16:44:51 UTC
This bug was reported to the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414909

"If i have a block of text in a plain text file like this:

****** ******** kjdksfjklsdjfkldsj
111111111 2222222222 3333333333
########## aaaa aaa  aa
kjdksfjklsdjfkldsj * ******** ****** **

I can't use ctrl+left-arrow to jump from the 'k' in the first line to the
beginning of the line.
Similarly from the first 'a' in line 3 to the start of that line.
Yet I can do this when the text consists of regular alphanumeric
characters such as the 1's in line 2.

I would want to do this kind of of operation when using
ctrl+shift+left-arrow to highlight text for copying.

If I were at the first 'a' in line 3 and used ctrl+left-arrow it would put
the cursor at the first '3' in line 2, rather than at the first '#' in
line 3; which is what it would do were I to do this at the first '2' in
line 2.
Perhaps this relates to why I am seeing the latter bug.

ctrl+left-arrow from the end of line 4 would take me to the beginning of
line 4 rather than to the next space amongst the '*'."
Comment 1 Alan Baghumian 2007-05-02 08:49:00 UTC
The same behavior on gedit 2.18.1.
Comment 2 Robert Roth 2011-07-04 16:58:01 UTC
I still get the same behavior as described above on gedit 3.1.1.
Comment 3 Paolo Borelli 2011-11-27 16:32:03 UTC
cursor movement is part of gtk
Comment 4 Sébastien Wilmet 2014-04-10 15:33:39 UTC
The root of the problem is bug #727972.

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