![]() ![]() VSCode automatically enables Git support for working copies instead of prompting you into oblivion.VSCode uses the stage, unlike WebStorm.You will likely want to install the Git extension pack, due to VSCode’s basic client implementation.Next, I’ll run Mocha’s test suites to prepare for publishing. Not the nicest initial experience, but I’m confident it’ll be smoother sailing from here. I go ahead and commit everything (including unstaged changes this would be Git: Commit All if I wanted to avoid the prompt), and push. VSCode uses the stage, like literally every other Git client except WebStorm’s. If you only use WebStorm’s built-in version control client (I don't), this will be culture shock. But I’m prompted that the stage is empty. I find Git: Commit via the Command Palette, and realize I could have used my trusty ⌘-K. VSCode helpfully marks the file with a big M in the file list. I’ve made my changes to CHANGELOG.md, and it’s time to commit. The presentation of the repo is a little disorienting (there are so many trees, it's like a forest), but I do see the pulled changesets. GitLens then provides Git history in the left sidebar. Hint: run GitLens: Toggle Code Lens and GitLens: Toggle Line Blame Annotations from the Command Palette. GitLens does some oddball things like “inline blame” and “code lens” (which is another view into “blame”? I don’t get it). To VSCode’s credit, it aids discovery with tags, filters and sorting. This is a drawback of the “small core” philosophy of VSCode (this reminds me of the Node.js ecosystem). But there are many Git-related extensions for VSCode. GitLens seems to solve this problem (and others). After searching in vain, I realize that there is no built-in support for Git history, and I’m going to need to grab an extension for this. Which changesets did Git pull? I want to look at the history. I think it worked? It said "sync." What's a "sync"? To pull, I found a little “refresh” button in my status bar, and clicked it. Happily, VSCode understands this is, in fact, a working copy. But I know origin has changes I need to pull. OK, so I want to edit Mocha’s CHANGELOG.md. It’s difficult to discover what a particular keystroke does at any given time, but also supports conditionals, for a nearly absurd level of control. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |