Skip to content
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

Closed
rking opened this issue Feb 6, 2013 · 1 comment
Closed

Reconsider all bindings #51

rking opened this issue Feb 6, 2013 · 1 comment

Comments

@rking
Copy link

rking commented Feb 6, 2013

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.

@Valloric
Copy link
Member

Valloric commented Feb 6, 2013

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.

@Valloric Valloric closed this as completed Feb 6, 2013
Grimy pushed a commit to Grimy/YouCompleteMe that referenced this issue Dec 22, 2014
Empty string is not valid JSON.

Fixes ycm-core#51.
@hardboydu hardboydu mentioned this issue Jul 4, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants