-
Notifications
You must be signed in to change notification settings - Fork 60
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
Move opens fold #3
Comments
Can try it yourself with a simple file containing this:
|
When all folds in there are closed. Just go to the first line and move it down to replace the second. The last fold will open. And then go to the last fold to close it again but it will not work as no fold is recognized. |
Sorry for the late response, I've been on vacation. I use folds myself and this would affect me, however I cannot replicate this behaviour. When I close all folds in your example above (or my vimrc) I can exchange the topmost lines just fine. Maybe some other fold-related plugin is causing this? However, there is a big problem when trying to move folds but this is worth a separate ticket. |
I edited your vimrc and nothing opened when moving lines in the upper portion. So, I guess one of the plugins may mess with the fold settings somehow. But it's a bit too much asked, to find out which one. |
Well seems so. I will try it out which one is the guilty by disabling them all and enableling them one after the other again. Thanks. |
I don't like to close it for that reason, but still: works for me. |
It may be useful. |
The MoveVertically commands now behave more similarly to j and k with respect to folds. We now move past closed folds instead of moving the lines inside them. I think this fixes matze#3.
I have several folds in my vimrc (with {{{ and }}}) to keep an overview about the stuff in there. When I use vim move in the upper part of the document it opens the last fold. After it is opened the fold is no longer recognized as fold so it can not be closed anymore. I am using vim 7.4
The text was updated successfully, but these errors were encountered: