Add an option to disable key bindings

Hey,

Would you be willing to add an option to disable binding keys? (Apologies if it exists already, I only see g:jedi#auto_initialization = 0 but that disables more than just mappings).

I know you can remap each key to make it use a different key, but that means that users have to go look up each map and pick some other key, even if they don’t care about it (i.e., I just want Jedi to not quash my mappings, I don’t really care about all the functionality it’s mapping).

Another alternative (or something to consider) based on the above would be to not map keys if they’re already mapped to something else.

[dbrodie]

I agree with @Julian, I would like a feature like this as well, especially since I don’t use jedi-vim as much by itself rather than integrate it into existing completion frameworks (such as deoplete, neocomplete) so that it is consistent with other languages I program in.

I think the best solution is to use the <Plug> mapping and have a setting to disable the mapping, or something equivalent.

[sloria]

Sorry to post on an old issue, but I still think this would be a useful feature. I, too, was looking for an option to disable setting of the default keymappings (without turning off other initialization steps, e.g. omnifunc).

That said, I respect that you want to keep jedi-vim’s configuration/API small.