Summary: | Unable to map accented key (ö on a Finnish keyboard) in Vi-mode | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | tlauniainen |
Component: | Vi Input Mode | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kdedevel, larsivar, michal.humpula, sami |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kate/9d06f5bcdc4a28b7f58028e4d3f7a31a26a7c9e1 | Version Fixed In: | 3.13 |
Sentry Crash Report: |
Description
tlauniainen
2012-04-24 09:09:35 UTC
tlauniainen: can you please test again with latest Kate by following http://kate-editor.org/get-it/ ? I have this issue too, only that my problematic key/character is 'ø'. I've had a similar issues with the FakeVim plugin in QtCreator, and part of the resolutions there has been bug fixes in Qt itself, handling non-ASCII characters properly. Do either of these characters require Alt Gr? On my Norwegian keyboard (and I think the Finnish too), these characters are first class letter keys, along with stuff like j, k and l. tested on switched keyboard layout to Finnish with KDE config. On finish keyboard the "ö" is regular key. Moreover in the non-vi mode of kate the character gets inserted to text as expected. In vi-mode insert mode the ";" (english key) is inserted instead. Git commit 9d06f5bcdc4a28b7f58028e4d3f7a31a26a7c9e1 by Michal Humpula. Committed on 29/11/2013 at 19:31. Pushed by michalhumpula into branch 'master'. vi-mode: make Finnish keyboard work properly This commit is potentionally breaking non-latin keyboards behaviour. On the other hand tests for it are not present and manual confirmation in vim/gvim also failed. REVIEW: 114212 M +3 -147 part/vimode/katevikeyparser.cpp M +0 -1 part/vimode/katevikeyparser.h M +17 -0 tests/vimode_test.cpp M +1 -0 tests/vimode_test.h http://commits.kde.org/kate/9d06f5bcdc4a28b7f58028e4d3f7a31a26a7c9e1 *** Bug 329370 has been marked as a duplicate of this bug. *** |