The navigation features look straightforward, but, at first glance, they don't seem very useful. So, for this part of the tutorial I suggest you on...
For further actions, you may consider blocking this person and/or reporting abuse
I move back and forth between Windows (at work) and Mac (at home) a lot. The thing that always melts my mind is VS Code shortcuts that are almost the same (e.g.
ctrl + bvscmd + b), and short-cuts that are completely different (e.g.ctrl + k, svsopt + cmd + s). T_TAlso,
ctrl + shift + pto open the command palette is a good one.I wonder why they chose to do this... On Windows, some of them are very similar to Visual Studio's shortcuts.
Opening the command palette is one of the shortcuts I always forget due to using
CTRL+Pand just prefixing my search with>.That is the sole reason I didn't recently replace my old work laptop with a Mac. I couldn't get over how nonsensical the apparently random switches between
cmdandctrlwere.Great post, shortcuts are THE BOMB.
I consider myself a avid shortcut user and here are some more:
ctrl + r: open recent projectctrl + q: open views panel (release ctrl to select)ctrl + b: toggle side panelctrl + shift + g: open source controlctrl + shift + x: open extensions panelctrl + shift + e: open project explorerctrl + shift + f: open search panelctrl + \`: toggle terminalctrl + shift + \`: open new terminalctrl + p: go to filectrl + n: start new filectrl + shift + n: start new VS Code instancectrl + shift + c: open external terminal on current project rootctrl + w: close current filectrl + pageup/pagedown: navigate to next/previus opened fileThere are a lot more shortcuts, but these are the ones I use the most.
These are great. Another one I use if using split view:
ctrl + [1, 2, 3...]: Focus the [first, second, third...] open panel. Splits to create another panel if one doesn't exist.