Thursday, December 19, 2019

Re: map j to non-latin1/utf-8 character

Hello,

I would like inform that problem may not be related using utf-8 or non-ascii character. I have seen the same behavior when I try to exchange j and k behaviors. k is working but not j.
I appreciate any insight or suggestions.

nnoremap j k
nnoremap k j


On Thu, Dec 19, 2019 at 11:50 PM Bilinmek Istemiyor <benibilme@gmail.com> wrote:
Hello,

I am using a Turkish-F keyboard layout. I would like to map "j" to Turkish "ü" character.  But also "k" to "j" since it is more convenient and natural for  me. (I know this is bad in the long run etc., but I have decided to do that)

I have put in my .vimrc file following commands

set encoding=utf-8  " The encoding displayed.
set fileencoding=utf-8  " The encoding written to file.

nnoremap ü k
nnoremap k j

k works as expected, however "ü" does not work. "ü" stucks after moving two lines above the current line.

Any help much appreciated.


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/34273057-d668-46df-829a-9f9591a65779%40googlegroups.com.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAB%3DHgN1bnPM2nrBJ3zqmK8mqBHzbnYCQAqcJgOd28M1_tRBr3w%40mail.gmail.com.

No comments: