-
Notifications
You must be signed in to change notification settings - Fork 52
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
Use silent! execute and <unique> to create non-clobbering mappings? #88
Comments
kshenoy
changed the title
Use silent and <unique> to create non-clobbering mappings?
Use silent! and <unique> to create non-clobbering mappings?
Sep 14, 2014
kshenoy
changed the title
Use silent! and <unique> to create non-clobbering mappings?
Use silent! execute and <unique> to create non-clobbering mappings?
Sep 14, 2014
Good points! I will check the conflicts and respond here again. |
Here are the options you currently have: Disable let g:targets_nlNL = 'nN ' Disable let g:targets_separators = ', . ; : + - = ~ * # / \ | & $'
let g:textobj_line_no_default_key_mappings = 1
xmap a_ <Plug>(textobj-line-a)
omap a_ <Plug>(textobj-line-a)
xmap i_ <Plug>(textobj-line-i)
omap i_ <Plug>(textobj-line-i) I will consider using |
Thanks for the prompt response! 👍 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I started using vim-textobj-line again and I realized that its mappings conflict with that of this plugin. Since, I've been using n/l for next/last for quite some time now, I changed textobj-line's mappings to use
_
since_
kind of represents a line-textobj. However, this still conflicts with targets.vimWould it be possible to use
:silent! execute
and<unique>
while creating the maps so that any user-defined mappings are not overwritten?I was also reading your response here and was intrigued by the idea of using n/N instead of n/l. Is this something that you have tried or plan on supporting? If not, I'll just hack it in my work-area and see how it feels.
Thanks for an awesome plugin :) 👍
The text was updated successfully, but these errors were encountered: