You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm trying to navigating within a typescript file using the [[ and ]] commands, that are supposed to move by "section". I'm not clear exactly what a section is but in Zed it moves by a chunk of code, like one function to another. According to Neovim docs a section has some kind of relation to { symbols. But in VS Code, [[ and ]] move to the beginning and end of the TypeScript file, and the number I put at the beginning seems to have no effect.
To Reproduce
Open up any large typescript file. Put the cursor in the middle of a chunk of code. Press [[ or ]].
Expected behavior
Moves by some reasonable chunk of code, like function to function or statement to statement. I'm not familiar enough with VIM and Neovim to know exactly what it should do.
Environment (please complete the following information):
Extension (VsCodeVim) version: 1.29.0
VSCode version: 1.96.0
OS: MacOS
Additional context
None
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm trying to navigating within a typescript file using the [[ and ]] commands, that are supposed to move by "section". I'm not clear exactly what a section is but in Zed it moves by a chunk of code, like one function to another. According to Neovim docs a section has some kind of relation to { symbols. But in VS Code, [[ and ]] move to the beginning and end of the TypeScript file, and the number I put at the beginning seems to have no effect.
To Reproduce
Open up any large typescript file. Put the cursor in the middle of a chunk of code. Press [[ or ]].
Expected behavior
Moves by some reasonable chunk of code, like function to function or statement to statement. I'm not familiar enough with VIM and Neovim to know exactly what it should do.
Environment (please complete the following information):
Additional context
None
The text was updated successfully, but these errors were encountered: