-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Cursor movement (not jump) opens newly folded range #8939
Comments
I think what you described is the expected behaviour in VSCodeVim and you can use You can create a remap in your
|
So if I'm understanding you correctly, this difference in behaviour from vim is expected? And why this change? If I'm creating a fold it generally means I know I don't want to look at them unless specifically to, but now that in VSCodeVim the most frequently used cursor moving keys (j/k) will simply expand this. Why is the default behaviour here instead of what vim is doing? |
I can't say for certain why it's implemented this way in VSCodeVim as I didn't write it, but anyway you can always remap it. |
you can add this settings:
to fix the fold bug |
Describe the bug
Cursor movement across folded ranges unfolds the lines, instead of move over the folded range like a single line (which is what this was intended to be in vim).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In VIM, cursor will be moved to the next line after the newly created fold in step 1
In VSCodeVim, moving cursor (j/k) will unfold and move the cursor into the unfolded, "physical" line.
Screenshots
If applicable, add screenshots to help explain your problem.
If remapping-related, please attach log output: https://github.com/VSCodeVim/Vim#debugging-remappings.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: