Conversation
This fixes an issue arising from use of normal instead of normal! inside the text object function. normal! is used in all places except one, the final gv. The result is that if a user has remapped built in VIM commands (gv, in this case), indent objects will not work correctly.
This adds an option, g:indent_object_no_mappings, which users may set to prevent vim-indent-object from defining any mappings. To allow users to then define custom mappings, we add <Plug> mappings for each of the objects. The default setting is to retain previous behavior, and define mappings.
|
Hi Alex, Thank you for your pull request. I have to apologize however, I really Michael On 13 February 2014 06:15, Alex Roper notifications@github.com wrote:
|
|
Sorry to hear that. Thanks for letting me know. |
This pull request allows users to define their own mappings by adding an option to prevent default mappings, and defining mappings to allow users to easily define their own. This also fixes what I believe to be a bug in how the area is selected due to use of normal instead of normal! (as elsewhere in the function) which arises when VIM's gv is remapped.