Earlier quoted context omitted.
A colleague uses it on OSX, and it's awful: unstable, crashes, hangs during debugging, the debugger doesn't always update the displayed values, doesn't grok auto declarations, etc. So far, Netbeans is the best free C++ IDE I've tried.
What about KDevelop?
Visual Studio Code 1.4
141–150 of 155 posts
Re: Visual Studio Code 1.4
#142What would be some of the cool features that only exist on VSC that Sublime doesn't have?
The cool telemetry phone home features that cannot be turned off in a reliable way (think updates). It's the feel good vibe that runs through all new MS apps and Win10. We should thank the third CEO for his great vision and be happy to give him all insight he needs. He is clearly steering his thriving platform to the next level.
Re: Visual Studio Code 1.4
#143I'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…
Edit: it looks like an issue about tasks.json presents some good examples: https://github.com/Microsoft/vscode/issues/981
Edit2: and here's the information about variables: https://code.visualstudio.com/docs/editor/tasks#_variable-su...
Re: Visual Studio Code 1.4
#144Visual Studio Code is currently my favorite editor. Fast, informative intellisense, great debugging environment, good git integration, faster than Atom, etc.
Fast? Really? What are you comparing it to?
Re: Visual Studio Code 1.4
#145Earlier quoted context omitted.
That's funny, I don't know that it's been referred to as an IDE so much as a more advanced code editor.. which is about all I use it for... I generally have my rightmost screen with iTerm and 3 windows split, one tall, the other two quarter screen... next to the left is VSCode for the project/directory I'm in, left again for browser, left for lync/outlook etc. As a code editor, I've really liked VS Code.. I haven't e…
You should be able to get most of the old behavior back by adding this to your settings.json: `{"workbench.editor.showTabs": false, "explorer.openEditors.visible": 10}`
Re: Visual Studio Code 1.4
#146Earlier quoted context omitted.
Agreed, I kind of wish that MS could come up with a way to get rebase/squash and pull --rebase working in the editor, having a 3-way merge in VS Code would be awesome... unfortunately it doesn't work well as a system editor choice for git cli. Been very happy with VS Code, though I wish I could revert to pre-tabs file behavior, I'd like the space back... it took getting used to, but the list switcher was a better UX…
> I wish I could revert to pre-tabs file behavior Adding the following to your User Settings should get you pretty close: { "workbench.editor.showTabs": false, "workbench.editor.enablePreview": false, "workbench.editor.enablePreviewFromQuickOpen": false, // ... }
Re: Visual Studio Code 1.4
#147I'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…
Would you expand on tasks.json? Where would I learn more besides docs, are there any specific source files? Does it support passing variables like the current file? Would you mind sharing your tasks.json? Edit: it looks like an issue about tasks.json presents some good examples: https://github.com/Microsoft/vscode/issues/981 Edit2: and here's the information about variables: https://code.visualstudio.com/docs/editor/…
Re: Visual Studio Code 1.4
#148Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.
I wanted to use VSCode when I started writing TypeScript three months ago, but I found the Vim plugins super lacking, so I used Atom instead, which has a much more robust Vim plugin. However, I tried VSCode again last week after being disappointed by continued bugs in atom-typescript, and was happy to discover the Vim plugin ( https://github.com/VSCodeVim/Vim ) had made a ton of progress since I'd last given it a sho…
Re: Visual Studio Code 1.4
#149Still 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
#150Earlier quoted context omitted.
> I wish I could revert to pre-tabs file behavior Adding the following to your User Settings should get you pretty close: { "workbench.editor.showTabs": false, "workbench.editor.enablePreview": false, "workbench.editor.enablePreviewFromQuickOpen": false, // ... }
Cool, thanks, anything to re-integrate left/middle/right into a single list again?