Bug 348663 - VIM ctrl-left-arrow and ctrl-right-arrow to jump between words not working
Summary: VIM ctrl-left-arrow and ctrl-right-arrow to jump between words not working
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: keyboard (show other bugs)
Version: 3.0.1
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-03 19:18 UTC by Gregor Leskovšek
Modified: 2017-11-13 07:28 UTC (History)
3 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 Gregor Leskovšek 2015-06-03 19:18:46 UTC 
In VIM  7.4 (2013 Aug 10, compiled Dec  9 2014 17:36:18) in Hp Probook 4730s since updating to Kubuntu 15.04 the ctrl-left-arrow and ctrl-right-arrow shurtcuts to move/jump between words ARE NOT WORKING ANYMORE.

These shortcuts are still working in Kate, but I noticed that the Ctrl++ and Ctrl+- are NOT working anywhere if I press plus or minus on numeric keypad BUT IS STILL WORKING EVERYWHERE if I press the plus or minus on main keypad. In previous Kubuntu 14.10 and lower worked also on numeric keypad.


Reproducible: Always

Steps to Reproduce:
1. vim savedfile.whatever
2. ctrl-left-arrow
3. ctrl-right-arrow

Actual Results:  
moving ctrl key wasn't pressed

Expected Results:  
jump to next/previous word
Comment 1 Aniketh 2017-01-21 13:08:30 UTC 
I don't think this bug do exist in Kubuntu 16.10, in Konsole version 17.03.70 . With Vim Version 7.4.1829. Hence, I would recommend making this bug status resolved. Else we can work on this.
Comment 2 George R. Goffe 2017-11-13 07:25:15 UTC 
This problem exists with vim-enhanced-2:8.0.1283-1.fc28.x86_64. It also exists with command line editing. see bug id 386841.
Comment 3 George R. Goffe 2017-11-13 07:28:03 UTC 
I forgot to add that this is a Fedora 28 rawhide system. The problem first appeared with Fedora 27. bugzilla.redhat.com has this bug as well, https://bugzilla.redhat.com/show_bug.cgi?id=1507337