221–230 of 231 posts
Earlier quoted context omitted.
Hi John, I've spoken with a few of the devs in our team having trouble with VS 2015 update 3 crashing. They'd love to switch to VSCode but ask: 1. When is there going to be decent C#/razor-intellisense, a razor generator ? 2. Will there be TFS integration (not git)?
I'm just the developer of VSCodeVim. I don't work on VSCode at all outside of that, so unfortunately I can't help you there. :)
Earlier quoted context omitted.
debugging is the best I've ever experienced. Webstorm debugging was problematic for me a year and a half ago. Visual Code has surpassed Atom by far as well, which weirdly does NOT support client side debugging for javascript (and that's a major mistake on Atom's behalf). In VSCode debugging is of course provided by 3rd party packages, but their API and rich debugging GUI seems to make it extremely easy to hook into i…
Same here, but for Firefox (which I prefer for WebDev). Just switched to VSCode because it's the only editor[1] that has a working JS Debugger for it: https://github.com/hbenl/vscode-firefox-debug [1] Though other editors might follow. Just saw that the Firefox Debugger team would be interested in integrating their new react/redux based debugger into Atom: https://twitter.com/clarkbw/status/783358566858010624
Earlier quoted context omitted.
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!
VSCode's C++ plugin supports both gdb and lldb (at least on macOS). As for what to learn--I'd learn GDB. Pretty much every architecture on the planet has a GDB port.
Earlier quoted context omitted.
I have little experience with both, but the developers of LLDB have a goal of making more informative error messages. This was successful enough that GDB devs were compelled to mimic this behavior, making their error reporting more accessible. As far as I know, LLDB still has the advantage in this regard.
You must be confusing LLDB/GDB with Clang/GCC. LLDB and GDB are debuggers, they generally do not produce many error messages. Clang has/had better error messages than GCC.
Earlier quoted context omitted.
I'm just the developer of VSCodeVim. I don't work on VSCode at all outside of that, so unfortunately I can't help you there. :)
Ok, if you can't relay it internally where is best to ask?
Earlier quoted context omitted.
Is Ctrl+X what you're looking for? Maybe you can change the binding of that.
Thanks, that is what i was looking for. Feel a bit silly for not noticing it, but it seems like an unusual behavior to associate with the 'cut' shortcut.
Earlier quoted context omitted.
Same here, but for Firefox (which I prefer for WebDev). Just switched to VSCode because it's the only editor[1] that has a working JS Debugger for it: https://github.com/hbenl/vscode-firefox-debug [1] Though other editors might follow. Just saw that the Firefox Debugger team would be interested in integrating their new react/redux based debugger into Atom: https://twitter.com/clarkbw/status/783358566858010624
Would you say the Firefox debugger works equally well as the Chrome variant? (In terms of responsiveness, integration, overal experience). I really fancy the JS debugger of VSCode but I'd hate to drop Firefox for that.
> Would you say the Firefox debugger works equally well as the Chrome variant?
Are you talking about the native debugger. Not sure. I only use the Chrome debugger from time to time, but mostly use the Firefox debugger. So it's ok, but since I use it all the time, I know it has its warts...
Anyway, there are completely rebuilding it using react.js at the moment: https://hacks.mozilla.org/2016/09/introducing-debugger-html/
> (In terms of responsiveness, integration, overal experience).
As said I use it (firefox and vs code) all the time as a JS developer.
> I really fancy the JS debugger of VSCode but I'd hate to drop Firefox for that.
That's the part I really do not understand. I do use Firefox (and its native devtools), and I do use VSCode plus its Firefox extension. So no reason to drop Firefox ;)
Is there a good VS Code extension / built in support for function / method list on a separate side bar? Something similar to Structure view in Webstorm or Function List in Notepad++? I learned that Ctrl-Shift-O will show functions but it is a not a permanent view.
Maybe I will port my Atom plugin ( https://atom.io/packages/atom-lupa ) to VSCode or maybe I'll write from scratch whole thing.
I don't know when exactly though (now I'm making something bigger than that and it takes time).