You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello -- seems like a simple quality of life change for those who, like I, are used to going up and down popups with j and k or and and accepting options with a press of "ret". This goes for navigating menus in general but I have personally found it a bit jarring to be unable to do this. If possible, please add :)
The text was updated successfully, but these errors were encountered:
This behavior was removed in #1704. If ret accepts the first item in the completion menu, you can't insert newlines while the completion menu is open. This makes editing very unpredictable for some languages.
I think the ideal way to fix this might be to allow menu keybindings to be configurable.
Absolutely -- I wouldn't say even make this default if folks don't want that. Perhaps just include a config option. In my bvim cmp opt I just have this little bit. Never had trouble with this combination:
I second this, having a way to automatically choose the first autocomplete option would be a great boon to people who were already using that function in neovim. But if ret becomes problematic as a default, how about enabling picker commands as normal commands so people can bind them in the config for example:
[key.insert]
C-o = ["next_entry", "select_entry"]
This way you would be able to select the first autocomplete when hitting Ctrl O
Hello -- seems like a simple quality of life change for those who, like I, are used to going up and down popups with j and k or and and accepting options with a press of "ret". This goes for navigating menus in general but I have personally found it a bit jarring to be unable to do this. If possible, please add :)
The text was updated successfully, but these errors were encountered: