ini files, but changing settings is often a chore). No longer we are bound by describing to what menu you have to go to click on which button (love you JetBrains and I know you have your. json, which is genius, because you can easily share and copy settings between users or projects no hassle. Luckily, there was a simple solution.Īnother great feature of the VSC is customizability in its settings file. So when I am building markdown documentation with mkdocs and I need to load my base environment, I couldn’t run it in the VSC prompt. Another issue is that for some reason, I couldn’t change the VSC anaconda environment using the anaconda’s activate *env* command and it was still defaulting to the root. I install almost nothing in the root environment, which is the default one that command prompt starts with when you open it. I use Anaconda as it was recommended, therefore installing packages in separate environments for different purposes (see list of some of my envs here). The main issue I came across was to run python code in Anaconda. So now you have VSC running and you can prototype your code nad run it from the same window, amazing. I already sang praise about Chocolatey here, and it is a must for a Windows based programmer in my opinion.

If you run Windows, you might be slightly underwhelmed by the command prompt capabilities, until you install Chocolatey. If you have Linux or a Mac, you are solid. VSC has somehting that I just fell in love since the first time I used it, and that was the integrated terminal.

Atom always seemed sluggish, despite all my effort and even PC upgrade, and sublime was nice and fast, but it just misses bunch of programming features. I tried Atom, I tried Sublime, I use Notepadd++ for text editing, but for javascript coding, markdown, blogging and occasionally python coding I use VSC.

How to run anaconda environment in Visual Studio Code terminal

Anaconda visual studio code