Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

f motion does not work well with vimRelayout #751

Open
laMudri opened this issue Apr 12, 2015 · 4 comments
Open

f motion does not work well with vimRelayout #751

laMudri opened this issue Apr 12, 2015 · 4 comments

Comments

@laMudri
Copy link

laMudri commented Apr 12, 2015

I use vimRelayout in the way shown in example-configs/yi-vim-colemak, but have the more conservative relayout V2.relayoutFromTo "hjk,:ʃɛʒə" "khj:,cejy". I've noticed that pressing fh causes the cursor to move to the next ‘k’, not the next ‘h’ (and similar with all of the other letters being remapped here). I'm fairly sure that this is not the desired effect, and there's no reason to relayout the keys for operator pending mode in the same way as in normal mode.

@jhance
Copy link
Member

jhance commented Apr 12, 2015

This is actually a motion and doesn't go through operator-pending mode.

@ethercrow
Copy link
Member

With colemak relayout to jump at character I press qwerty f (because I have muscle memory for that particular vim action) and then desired colemak letter (because I no longer remember where qwerty letters are). So I think moving to k in your case is normal.

@laMudri laMudri changed the title vimRelayout affects operator pending mode f motion does not work well with vimRelayout Apr 13, 2015
@jhance
Copy link
Member

jhance commented Apr 13, 2015

@ethercrow but isn't that exactly what is not happening? I believe the problem is that he presses 'fh' (the dvorak keys, with 'f' not remapped at all), and it moves to 'k' because of the remap

@ethercrow
Copy link
Member

Yes, I was in a fairy land at the moment and described what should happen instead of current reality. We do indeed have a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants