Cursor movement (not jump) opens newly folded range about vim

[HenryTSZ]

you can add this settings:

"vim.foldfix": true,

to fix the fold bug

[shinohara-rin]

I think what you described is the expected behaviour in VSCodeVim and you can use gj and gk instead of j and k to achieve what you expected.

You can create a remap in your settings.json with something like this:

"vim.normalModeKeyBindingsNonRecursive": [
    {
        "before": [
            "j",
        ],
        "after": [
            "g",
            "j"
        ]
    },
    {
        "before": [
            "k",
        ],
        "after": [
            "g",
            "k"
        ]
    }
],

[wolf0403]

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?

[shinohara-rin]

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.