But just being able to type some code, set a breakpoint, run to it, and inspect some locals makes me so much more productive than the Printf driven debugging that so many masochists still cling to.
Visual Studio Code 1.4
71–80 of 155 posts
Re: Visual Studio Code 1.4
#72I'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
#73Visual Studio Code is currently my favorite editor. Fast, informative intellisense, great debugging environment, good git integration, faster than Atom, etc.
Re: Visual Studio Code 1.4
#74Whenever 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…
Re: Visual Studio Code 1.4
#75Earlier quoted context omitted.
Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.
I'm curious, what's the thought behind having an official company-wide text editor? The companies I've worked for usually take the route of "leave their choice in tools up to them", which I appreciate.
Re: Visual Studio Code 1.4
#76I'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…
What are some of the custom tasks you've been using in it? I've found I'm using the integrated terminal significantly more than I ever did with the tasks, but maybe I'm missing something really cool.
Re: Visual Studio Code 1.4
#77What would be some of the cool features that only exist on VSC that Sublime doesn't have?
Re: Visual Studio Code 1.4
#78Re: Visual Studio Code 1.4
#79Earlier quoted context omitted.
Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.
How did you manage to leave vim keys so easily?
Re: Visual Studio Code 1.4
#80Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.