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

What completeopt do people use? #116

mtglsk opened this Issue Mar 24, 2016 · 1 comment


None yet
2 participants
Copy link

mtglsk commented Mar 24, 2016

Do people change this? I find the default autoselection extremely irritating (menu, preview). It's really not that obvious for a newcomer to know how to cancel a selection (and vim's omnicomplete is quite complicated as it is) so you tend to BS through the change and then go google on how to cancel a completion ;). Most ide's etc. show the balloon but don't autoselect a completion unless you want to (like ctrl space to show completions, then ctrl space again to autocomplete).

I personally use noselect, menuone, preview but something like completeopt+=longest is also imho better than default.


This comment has been minimized.

Copy link

tpope commented Mar 24, 2016

That's a pretty good example of why the editors in most IDEs are a joke tbh. You want to add an extra keystroke to every single completion just so someone doesn't have to learn how to cancel an insertion?

rliang added a commit to rliang/vim-sensible that referenced this issue Jan 10, 2019

set completeopt+=menuone,noinsert,noselect
As seen in most configs.
Every plugin that deals with completion in some way also suggests or requires this.
Closes tpope#116.

@tpope tpope closed this Jan 10, 2019

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