![]() Key bindings are at once more powerful and complex than WebStorm.If you're using the default bindings in WebStorm, you likely want to install the JetBrains IDE Keymap extension.Install “Extension Packs” to get started quickly.I go ahead and open up my Mocha working copy… Summary I am, however, elated to report that the JetBrains IDE Keymap is a thing, and it works great. ![]() Since C/C++ isn’t listed on the “Welcome Page”, I dig into to the extensions and … can’t help myself from installing a bunch of extensions. I want to avoid customizing too much at the outset. I ignore the web page (thanks, but no thanks) and click a few of the “Install support for…” links under Tools and languages to get some basic extensions installed. This takes ~4s on my 2016 MBP-but I don’t have any extensions installed yet. □ visual-studio-code was successfully installed! => Linking Binary 'code' to '/usr/local/bin/code'. => Moving App 'Visual Studio Code.app' to '/Users/boneskull/Applications/Visual Studio Code.app'. => Verifying checksum for Cask visual-studio-code I used Homebrew Cask to install it: $ brew cask install visual-studio-code I’m certainly interested in how VSCode handles Python and C/C++, but I’m not going to explore it in this post. I’ll be looking at this from the standpoint of a JavaScript developer, so I’ll write “WebStorm,” but I really mean “a JetBrains IDE.” How smart is it about types and code completion?.What’s the story on inline errors or warnings?.How does the VCS (Git) integration differ?.What’s debugging look like? How’s the source map support?.What’s the analog of a “Run Configuration?”.Does it support my key bindings, or will I need to relearn everything?.I'll answer some questions for myself-and, with luck, maybe I can save the JetBrains-faithful some time and energy. Something’s up, and I’m going to get to the bottom of it. I’ve been a faithful user since P圜harm’s release, seven years ago.Īs of late, if I’m watching a presentation, and someone is writing code in an editor, that editor is almost always VSCode.
0 Comments
Leave a Reply. |