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

moving between lines is not intuitive #283

Open
vindex10 opened this issue Nov 8, 2024 · 1 comment
Open

moving between lines is not intuitive #283

vindex10 opened this issue Nov 8, 2024 · 1 comment

Comments

@vindex10
Copy link

vindex10 commented Nov 8, 2024

Describe the issue:

Hi! I'm new to vim-visual-multi, but I have a question about the motions.

Steps to reproduce
I created a column with "ctrl-down". Then I can do "2l" or "2h" to move the column by 2 characters right or left.
I can also use jk to move one line up and down.

But 2k works as "^" instead
and 2j works as "$".

I would expect the cursors to jump two lines up or down.
Also doing <line no>gg to move the cursors to the line would be helpful.

I might be missing some important bit of the documentation, so would appreciate every hint :)

I tried with empty vimrc (with vim plug) in neovim:

call plug#begin('~/.vim/plugged')
Plug 'mg979/vim-visual-multi'
call plug#end()

  • Operating System: Ubuntu
  • Vim Version:
:version
NVIM v0.11.0-dev
Build type: RelWithDebInfo
LuaJIT 2.1.1703358377

same happens in vim

:version
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Sep 25 2024 10:13:04)
Included patches: 1-16, 647, 678, 697
  • commit SHA/branch: a6975e7 (master)
@satishskamath
Copy link

satishskamath commented Jan 15, 2025

I am also experiencing this with neovim. Up and down motions with number of lines does not work. I can only go one line up or one line down in the normal mode (multi-line off)

@vindex10 the way to make it work is to enable multiline mode using <leader-M> and then perform the Up and down motions with number of lines using 2j.

But indeed this is not intuitive, therefore it is worthy to be an issue, I think. :)

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

No branches or pull requests

2 participants