-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Does not open closed folds like vim's native commands #22
Comments
Without weighing in on whether or not this should be the default behaviour, you can solve this by making your own mappings with
|
Or, if you want to get really fancy... for mapping in [ "gz#", "z#", "g#", "#", "gz*", "z*", "g*", "*" ]
execute "map" mapping "<Plug>(asterisk-" . mapping . ")zv"
endfor |
I have done exactly that already, but vim-asterisk bills itself as "improved * motions". The default vim behavior is to open folds, and if vim-asterisk is breaking that, that's the opposite of an improvement. |
Some people may prefer them closed! :P Only kidding. I'm inclined to agree that it should not deviate from vim behaviour in this way. |
The native vim '*' command will open any closed fold in which the search term is located. But when I mapped '*' to the asterisk plugin, I see it only navigates to the closed fold which contains the term, but doesn't actually open it.
The text was updated successfully, but these errors were encountered: