I have been trying to use VSCode for languages besides JS, like C# and C++, but I've been getting stuck. There's a big opportunity here for someone to write up some brief tutorials on how to use VSCode for other languages. So far, the instructions are basically "Get VSCode. Enable the C++ extension. Enjoy!" That's not enough, especially when it comes to setting up debugging, which c'mon, everyone needs. The json conf…
Visual Studio Code 1.4
41–50 of 155 posts
Re: Visual Studio Code 1.4
#42This editor is also very good to write Golang code.
Re: Visual Studio Code 1.4
#43I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…
Re: Visual Studio Code 1.4
#44Re: Visual Studio Code 1.4
#45Re: Visual Studio Code 1.4
#46I felt bad for Sublime. It would be hard for Sublime to compete with MS's free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.
They are providing the same tools they use to drive VSC to many popular editors, including Emacs and Vim as well. It seems that Microsoft wants to give you the best support they can in whatever environment you like!
Re: Visual Studio Code 1.4
#47What would be some of the cool features that only exist on VSC that Sublime doesn't have?
For one, nice git integration. You can see lines added/changed/removed in the gutter, unobtrusively.
Sublime has a plugin that does something similar but it's not out of box and it's not as nice/polished.
This is just one thing.
Re: Visual Studio Code 1.4
#48Earlier quoted context omitted.
Intellisense? Autocomplete?
It isn't Intellisense since it isn't using type information but the context of the text buffer to determine possible completions. Autocomplete is too vague.
It's really vague, but I'd still call it autocomplete.
Some editors, like Notepad++, end up using whatever they can find as a means to autocomplete. So you end up with a huge list of suggestions for anything you type. But it's because they lack the power to analyze the code and actually know what's allowed where you're typing.
Re: Visual Studio Code 1.4
#49Still no auto-import on Typescript. The main reason I use Webstorm over VSCode currently. What I am talking about: * new Foo| * * (Automatically inserted by editor top of the file where imports are) import {Foo} from "../relativePath/to/Foo.ts" * new Foo(param);| Working on a large TS codebase without this is absurd. Webstorm is way ahead of VSCode in this area, including things like multiple named imports like: * im…
Re: Visual Studio Code 1.4
#50Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…