[SOLVED] remap "hjkl" keys on vi

Haythem · 11-20-2013, 02:24 PM

Hi, I want to map hjkl keys to jkl; on "elvis" because I started using "i3wm" and i3 actually using jkl; as arrows.
when I map the keys in ".exrc" file they are mapped recursively so they all map to ";". I could not find an option to map non-recursively.
changing i3 keys is easier but actually I think that jkl; is more convenient. also don't want to change to "vim" because I like to stick with slack's defaults.
Any ideas how to do this mapping? Thanks.

saulgoode · 11-20-2013, 04:41 PM

:nnoremap j h
:nnoremap k j
:nnoremap l k
:nnoremap ; l

EDIT: missed that you wanted to use vi instead vim. FWIW, vim is no less a Slackware default than vi.

TobiSGD · 11-20-2013, 06:24 PM

That Slackware has some defaults (just out of curiosity, which DE/WM do you use?) does not mean you shouldn't use what Slackware has to offer on other options. Slackware has Vim in the default installation, so it is as default as any other editor in Slackware.
By the way, I also use i3 and I have reconfigured it to use the Vim keys, since it is the only program I use that differs from the Vim keyboard scheme.

lems · 11-21-2013, 06:38 AM

Does this work:

Code:

set noremap
map j h
map k j
map l k
map ; l

(I personally use nvi, which was based on elvis.)

edit: /usr/bin/vi is a symlink to elvis on Slackware, so yes, it can be seen as the default.

Haythem · 11-21-2013, 08:49 AM

Quote:

Originally Posted by lems

Does this work:

Code:

set noremap
map j h
map k j
map l k
map ; l

my bad, I did the same thing but reversed the keys (map h j instead of map j h).
that solved the issue, Thanks Guys

Geist · 11-23-2013, 04:40 PM

Quote:

Originally Posted by TobiSGD

By the way, I also use i3 and I have reconfigured it to use the Vim keys, since it is the only program I use that differs from the Vim keyboard scheme.

This.
You can find Vi(m) binds for pretty much everything, changing your WM to use the same schema is a lot faster (and of course in the end more consistent) than changing all and every Vi(m) bind stuff you might come across in the future.