Visual Studio Code 1.8 • Hacker News Board

Re: Visual Studio Code 1.8

#141

Post by wwalser » Thu, Dec 15, 2016, 4:51 AM UTC

bitwize wrote: post #134

jordache wrote: post #124

Earlier quoted context omitted.

Emacs doesn't do go to definition? Eeek

Installing tern-mode from MELPA makes M-. for JS work in Emacs.

Didn't know this, will try!

Re: Visual Studio Code 1.8

#142

Post by Tyriar » Thu, Dec 15, 2016, 5:12 AM UTC

saghm wrote: post #123

lowmagnet wrote: post #109

Earlier quoted context omitted.

They just introduced keymap modes, including emacs.

Oh, not sure how I missed this! I'll have to try it out EDIT: On trying it out, it seems to have reasonable support for most of the editing functionality, but the shortcuts for handling split buffers (C-x 0, C-x 1, C-x o, etc.) is completely non-existent. I'm unsure right now whether I'd be able to define them on mine own or whether I'd be willing to stick with it if I couldn't.

If it's missing functionality you need you could request by filing an issue to https://github.com/hiro-sun/vscode-emacs

Re: Visual Studio Code 1.8

#143

Post by anupshinde » Thu, Dec 15, 2016, 5:55 AM UTC

Hot exit is finally here. I missed this feature when I moved from SublimeText. And very useful on desktops

Re: Visual Studio Code 1.8

#144

Post by cocochanel » Thu, Dec 15, 2016, 6:19 AM UTC

I switched to VS code today and I love it! Looking forward to JS improvements. Thank you to the Microsoft team! :)

Re: Visual Studio Code 1.8

#145

Post by Rapzid » Thu, Dec 15, 2016, 6:21 AM UTC

I wonder how much of VS Code's community momentum over Atom is due to TypeScript vs Coffee. Personally, I find code bases with great language tooling easier to jump into.

Re: Visual Studio Code 1.8

#146

Post by crooked-v » Thu, Dec 15, 2016, 6:23 AM UTC

WhitneyLand wrote: post #57

Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…

WebStorm on OS X has been slow and laggy every time I've tried it on a machine that can handle Atom and VS Code with no problems.

Re: Visual Studio Code 1.8

#147

Post by asadm » Thu, Dec 15, 2016, 6:51 AM UTC

mini-map is the only thing stopping me from jumping to VSCode.

Re: Visual Studio Code 1.8

#148

Post by Ace17 » Thu, Dec 15, 2016, 6:55 AM UTC

miguelrochefort wrote: post #56

thenewwazoo wrote: post #41

Earlier quoted context omitted.

I'm not sure why not. AFAIK that's still your only option if you want to debug NodeJS code headlessly.

What about conditional break points, call stack, time travel, watch list, live editing, etc?

Wow, there are actually people using any of these?

Re: Visual Studio Code 1.8

#149

Post by nojvek » Thu, Dec 15, 2016, 6:56 AM UTC

tarr11 wrote: post #75

How do VSCode features get ported to the Monaco Code Editor[1]? I was interested in using it but noticed the last commit for Monaco was in October. [1] https://github.com/Microsoft/monaco-editor

the monaco editor code is part of vscode. They do a scripted copy to the repository every now and then. Definitely file an issue if its a bit too old.

Re: Visual Studio Code 1.8

#150

Post by nojvek » Thu, Dec 15, 2016, 6:57 AM UTC

nkg wrote: post #80

I want to love you, VS. Your name would look so good on my resume.I'm going to try one more time.

I don't work on vscode directly, have contributed bug fixes and features but if you'd like to be considered for a team inside visual studio working on web diagnostics, please ping me.