-
Notifications
You must be signed in to change notification settings - Fork 4
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
Key Binding Overwrites Important Default Mapping of Vim #15
Comments
I will check that. Thanks for reporting. |
Oh, I thought I have misunderstood you. You can define the keybindings in your vimrc. For Fortran90 menus, where
|
Please let me know if this solved your issue or revert back to me. |
This is not what i wanted to say. IMHO it is just not very smart for a plugin to overwrite a default vim command with something completely different. I would suggest to use the leader key of vim to initiate the commands of the plugin. Sure, I can rebind it, e.g. |
I agree it is not very good (or should be avoided by all means) to override default mappings. The keybinding is actually defined in most generic way possible as: |
I do have the |
Okay with Edit: I somehow was on the previous commit where it only worked with the
|
I don't know what your commands with |
The last commit has broken the default mapping of vim. For example I no longer can use the 'ce' command (create executable gets triggered). I guess something went wrong with the mapping of the leader key.
The text was updated successfully, but these errors were encountered: