Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.6

code.visualstudio.com

Post reply on HN
Print view View original

31–40 of 231 posts

Re: Visual Studio Code 1.6

#31

Post by steveklabnik »

tomdale wrote: post #3

I have been using VS Code as my full-time editor for a few months now and couldn't be happier. Originally I was only using it for TypeScript projects, where the language integration is top-notch, but eventually found myself using it all the time. I use the vim plugin, which is surprisingly good although it does have a few issues still. The best thing about VS Code (and Microsoft's other big open source project, TypeS…

They've been making so much progress on the vim plugin. I was recently at a conference, and was talking to someone who works on Code. The conversation went something like this:

Me: "I wanted to use Code, but the vim integration wasn't good enough."

Her: "Oh yeah? What issues did you have, specifically?"

Me: "Let me just reinstall real quick and I'll show you."

Me: "... okay yeah this just works now. Awesome."

Re: Visual Studio Code 1.6

#32

Post by equasar »

foldr wrote: post #17

I'd like to switch from Atom but a few little niggles make me keep going back. I like how Ctrl+K has the emacs-style behavior in Atom, and there's an annoying bug in VSCod's tex mode which stops commenting and uncommenting of lines from working.

You can override any key combination.

Re: Visual Studio Code 1.6

#33

Post by hockeybias »

eknkc wrote: post #29
tomdale wrote: post #3

I have been using VS Code as my full-time editor for a few months now and couldn't be happier. Originally I was only using it for TypeScript projects, where the language integration is top-notch, but eventually found myself using it all the time. I use the vim plugin, which is surprisingly good although it does have a few issues still. The best thing about VS Code (and Microsoft's other big open source project, TypeS…

It's indeed a fantastic editor. Replaced Sublime for me and I couldn't be happier.

Ditto!

Re: Visual Studio Code 1.6

#34

Post by CoryG89 »

david-given wrote: post #21
Achshar wrote: post #8

What I find to be hilariously missing is drag & drop for the selected text. I tried switching to VS code a couple of days ago and realized I couldn't do such a basic thing. That and a decent FTP extension. No one wants to sync their entire project just to upload a single file. ugh.

You use drag and drop of selections? I don't think I've ever done that on purpose --- every time I've ever dragged selected text has been by accident, followed by much cursing as I try to fix my mangled document. I'd turn it off system-wide if I could!

I would curse too if no one ever told me I could use Ctrl-Z to fix something like that.

Re: Visual Studio Code 1.6

#35

Post by niyazpk »

Can I use VS Code to work with remote files? I almost always work with remote files for development at my day job and would like to switch to VSCode for its better JS support. Right now I am using SublimeText3 with the rsub plugin to edit remote files.

What workflow do you guys use when working with remote files?

Re: Visual Studio Code 1.6

#36

Post by Cyph0n »

david-given wrote: post #20
tomdale wrote: post #3

I have been using VS Code as my full-time editor for a few months now and couldn't be happier. Originally I was only using it for TypeScript projects, where the language integration is top-notch, but eventually found myself using it all the time. I use the vim plugin, which is surprisingly good although it does have a few issues still. The best thing about VS Code (and Microsoft's other big open source project, TypeS…

I'm currently switching from gvim to vscode and back again every five minutes, in order to use vscode's debugger --- it's gdb integration is the best I've seen bar none [1][2]. If the vim emulation was good enough, I'd switch in a moment. Which, unfortunately, it's not, for me: the biggest omission is shift-Y/shift-P for yank and paste, which I use constantly, but there's holes everywhere. (Also, the way the vscode's…

Damn, seriously? I'm going to be writing some C++ soon, and I'm also planning to learn gdb, so I guess VS Code it is then. Thanks for the heads up!

Re: Visual Studio Code 1.6

#37

Post by steveklabnik »

Cyph0n wrote: post #36
david-given wrote: post #20

Earlier quoted context omitted.

I'm currently switching from gvim to vscode and back again every five minutes, in order to use vscode's debugger --- it's gdb integration is the best I've seen bar none [1][2]. If the vim emulation was good enough, I'd switch in a moment. Which, unfortunately, it's not, for me: the biggest omission is shift-Y/shift-P for yank and paste, which I use constantly, but there's holes everywhere. (Also, the way the vscode's…

Damn, seriously? I'm going to be writing some C++ soon, and I'm also planning to learn gdb, so I guess VS Code it is then. Thanks for the heads up!

There's also a brand-new lldb plugin too https://marketplace.visualstudio.com/items?itemName=vadimcn....

Re: Visual Studio Code 1.6

#38

Post by andrewingram »

I've been using VSCode for a few months now, I'm finding it to be really powerful. Main downsides for me:

* The Flow support (via an extension) is pretty far behind the TypeScript support, which is understandable but not ideal.

* It doesn't yet have the critical mass of mindshare for it to be primary target for extension authors, i'm hoping that changes.

* The lack of ability to customise/theme the UI means I can't do anything about the fact that my syntax theme looks totally out of place in the UI.

Re: Visual Studio Code 1.6

#39

Post by tomdale »

steveklabnik wrote: post #31
tomdale wrote: post #3

I have been using VS Code as my full-time editor for a few months now and couldn't be happier. Originally I was only using it for TypeScript projects, where the language integration is top-notch, but eventually found myself using it all the time. I use the vim plugin, which is surprisingly good although it does have a few issues still. The best thing about VS Code (and Microsoft's other big open source project, TypeS…

They've been making so much progress on the vim plugin. I was recently at a conference, and was talking to someone who works on Code. The conversation went something like this: Me: "I wanted to use Code, but the vim integration wasn't good enough." Her: "Oh yeah? What issues did you have, specifically?" Me: "Let me just reinstall real quick and I'll show you." Me: "... okay yeah this just works now. Awesome."

Most "vim emulation" plugins suck, because the vim way of thinking about things is so different from the typical GUI editor. Because of this, extension APIs often have to be wildly abused just to get even moderately decent parity with vim. Bugs and inconsistencies abound and are often impossible for the plugin author to fix.

That's why it's been extremely heartening to see releases of VS Code that explicitly add extension points to enable features for the vim plugin[1]. It's not perfect now, but given that the VS Code team seems to be making it their mission to offer an extension API robust enough to make it perfect, I'm willing to deal with the quirks for now.

[1]: https://code.visualstudio.com/updates/v1_5#_extension-author...

Re: Visual Studio Code 1.6

#40

Post by foldr »

equasar wrote: post #32
foldr wrote: post #17

I'd like to switch from Atom but a few little niggles make me keep going back. I like how Ctrl+K has the emacs-style behavior in Atom, and there's an annoying bug in VSCod's tex mode which stops commenting and uncommenting of lines from working.

You can override any key combination.

I looked into it, but it wasn't obvious how to:

(i) make Ctrl+K put the deleted line into the paste buffer.

(ii) allow repeated applications of Ctrl+K to delete multiple lines.

Post reply on HN