question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Moving up and down inside an auto-completion box through Vim keys (j and k) instead of arrow keys.

See original GitHub issue

FEATURE REQUEST: A feature which will make life inside the editor, of every VSCodeVim user, 100 times easier!

What happens: When we start typing some letters and intellisense opens the auto-completion box, if the choices are more than one and our required option isn’t under selection, we have either to type more letters to filter further and have our required member selected or press arrow keys to choose the required member manually and then press tab to insert it. Sometimes we even lose the choice of typing more characters to further filter. This kind of situation occurs in cases when we have a snippet and we have already completed the prefix for that snippet. For example the following snapshot. 01a

In the example above I have already completed typing the prefix (la) for an embedded elixir snippet, but as another member (Emmet Abbreviation for label tag) is above the required member, so I have to press the down arrow key to choose the required member.

(Important) Now if I press Escape key, it will discard the auto-completion options altogether and will take the editor (from the insert mode) to the normal mode. 02

What do I wish to happen: I wish that inside the auto-completion box, while being in the above situation (more than one members, and the required member isn’t under selection), if I press Escape key, the editor don’t go back to the normal mode, but it temporarily map j and k keys to to down and up arrow keys respectively, until I get out of the auto-completion box by either pressing tab to insert a member, or press Escape again to get out of the auto-completion box myself.

Thank You so much for this awesome plugin!

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:1
  • Comments:13 (4 by maintainers)

github_iconTop GitHub Comments

8reactions
IanEdingtoncommented, Feb 13, 2018

Ctrl n and Ctrl p is standard in vim (next prev). This would break that paradigm.

7reactions
Chilleecommented, Feb 13, 2018

I’m a bit confused what the purpose of this would be. Do you not want to use down and up?

If so, you can use Ctrl n and Ctrl p.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Scrolling in vim autocomplete box with jk movement keys
I know the question is asking to use the J and K keys but you can also avoid using the arrow keys another...
Read more >
Moving up/down on autocomplete selection box without ...
Yes, there is: Ctrl + p to move up. Ctrl + n to move down. Furthermore, these keybindings are not special to vscodevim,...
Read more >
Using Vim's Built in Complete Menu for Autocompleting Words
Getting a natural autocomplete experience without setting up any language servers.Hit the subscribe button to receive more videos like this!
Read more >
Vim/Vi Page Up and Down Controls
While the most intuitive way to navigate around the terminal may be scrolling and using the arrow keys, Vim offers multiple shortcuts to...
Read more >
How to navigate autocomplete popup without arrows? : r/vim
Heh, I wanted to be one of the cool kids so I remapped arrow keys to ... the many reasons I love having...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found