Skip to content

Instantly share code, notes, and snippets.

@BolajiOlajide

BolajiOlajide/GettingStartedWithJetbrains.md

Created October 7, 2022 13:51
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save BolajiOlajide/f61c1128413e35bfa933769c676680e3 to your computer and use it in GitHub Desktop.
Save BolajiOlajide/f61c1128413e35bfa933769c676680e3 to your computer and use it in GitHub Desktop.
Download ZIP
Things to know when switching to Jetbrains (especially from VSCode)
Raw
GettingStartedWithJetbrains.md

I recently started trying out GoLand for development, I've heard good things about the product from my colleagues at Sourcegraph. The one thing that caught my eye was the better intellisense it had. I decided to signup for a trial (even though we had a company license, I did this because I wanted to be sure I was going to use the IDE so I don't take up a seat).

One of things that first confused is that Cmd + P which I used to look for files in VSCode wasn't a thing in Jetbrain products.

Apparently, there's a VSCode keymap plugin for Jetbrains that can be used to remap your keys so it works like VSCode.

If you don't want to install the plugin, you can change the mapping yourself by navigating to Preferences > Keymap and search for “go to file” and update the mapping.

Command shift a is the action search - analog to the command palette

Thanks to everyone #jetbrains

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment