-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Reconsider all bindings #51
Comments
Sorry, but I disagree to an extent. Yes, chances are that if you have lots of other plugins installed, something is going to conflict. That's why you can remap all the keys. But you greatly overestimate the number of Vim users who have more than a couple of plugins. I have ~20 (probably more), but that's me though. You probably have a lot as well. But most people don't, and the number of people who have a conflicting plugin installed is even smaller. The default configuration should be built for the 90% use case and user. |
Empty string is not valid JSON. Fixes ycm-core#51.
The assumption that
i_<Tab>
,i_<S-Tab>
,<Leader>d
, etc., are all available to a new plugin is going to slow adoption. Many other tools already make use of these.I think we should figure out if there is a less-prominent set of bindings to use by default, and relegate the existing ones to the README.
The text was updated successfully, but these errors were encountered: