I know this post is a bit old, but I put these settings in all my VS Code configurations. One thing that I have an issue with is getting this kind of navigation to work from within .ipynb notebooks.
I've found that this works for left and right navigation:
I don't use notebooks in VS Code much so I didn't have any immediate insights, but your comment got me curious so I went looking for some :D. And the first place I landed was this open issue which you already commented on!
(At some point after writing this post, I moved my nav bindings into chords off ctrl+k only because I kept running into edge cases where I wanted ctrl+k available.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I know this post is a bit old, but I put these settings in all my VS Code configurations. One thing that I have an issue with is getting this kind of navigation to work from within
.ipynb
notebooks.I've found that this works for left and right navigation:
but there is no such action for
focusUpGroup
/focusDownGroup
, and I can't quite get this work work withnavigateUp
/navigateDown
or panels.Do you have any immediate insights as to how to accomplish this? Thanks for the great post!
I don't use notebooks in VS Code much so I didn't have any immediate insights, but your comment got me curious so I went looking for some :D. And the first place I landed was this open issue which you already commented on!
github.com/microsoft/vscode/issues...
I replied to your comment there, but you can add
focusAboveGroup
andfocusBelowGroup
bindings to make the workaround cover all directions:(At some point after writing this post, I moved my nav bindings into chords off
ctrl+k
only because I kept running into edge cases where I wantedctrl+k
available.)