-
Notifications
You must be signed in to change notification settings - Fork 411
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
select prev/next item mapping not working for cmdline case #809
Comments
You should change the mapping as following.
↓↓↓
|
Worked like a charm, thanks! |
As per hrsh7th/nvim-cmp#809. Not yet tested as I can only reproduce the problem inside Docker.
As per hrsh7th/nvim-cmp#809. Not yet tested as I can only reproduce the problem inside Docker.
hey! and But the up and down arrow keys seem to be still used to navigate through the autocompletion menu. Any hints ? |
Ok nevermind, this way of declaring the keymaps work: mapping = {
["<S-n>"] = cmp.mapping.select_next_item { behavior = cmp.SelectBehavior.Insert },
["<S-p>"] = cmp.mapping.select_prev_item { behavior = cmp.SelectBehavior.Insert },
}, (thx tj) |
FAQ
Issues
Neovim Version
0.6.1
Minimal reproducible config
Description
When I try to navigate to next/previous items in code (e.g. a
cpp
file) then theLeft
andRight
custom mappings work (I can navigate to previous/next items using left/right keys).However, if I enter command mode
:
then the left/right keys no longer work to navigate to prev/next items and I still need to use the tab key.Steps to reproduce
Open a
cpp
file and type#include
— note that left/right arrows navigate to prev/next items.Enter command mode via
:
and type in something to prompt auto-complete suggestions. Note that left/right arrows no longer navigate to prev/next items. Note that the tab key works to navigate items.Expected behavior
Left/right keys work to navigate between items in command mode.
Actual behavior
Left/right keys do not work to navigate between items in command mode.
Additional context
No response
The text was updated successfully, but these errors were encountered: