The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Does it not call a compiler? Does it not execute the executable? And can it not attach a debugger to the executing process? It's an IDE; just not a full-featured one.
"and leaves more complex workflows to fuller featured IDEs." -- Visual Studio Code FAQ
My hope is that it's more like the Turbo Pascal (4 and 5) IDE. Over the last few years I have developed a simple IDE of my own with only the features I need. Debuggers, syntax-highlighting, and Intellisense (though convenient when available) are not things I generally need.
Same opinion here. I like Notepad++, but there is a need for something simimilar on linux and especially for the people from the win-dev-world.
Please I know about 'vi', but it's not my 1st choice only tool... please!
Something about which we often break our head:
"In the name of the Compiler, the Stack, and the Bug-Free Code. Amen."
Sublime Text is still around for the Mac - shame it never got developed further than it did.
TextWrangler (free) is ok(ish) too if you're desperate, but VS Code does a decent enough job too. I tend to use WebStorm on the Mac though.
I came into this game for the action, the excitement. Go anywhere, travel light, get in, get out, wherever there's trouble, a man alone. Now they got the whole country sectioned off, you can't make a move without a form.
I gave it a spin but decided I liked Sublime better. Maybe it was because I only found one plugin that let me FTP-sync with the actual code base running on an Ubuntu VM, and I didn't want to be bothered with configuring yet another editor.
But there was also something definitely klunky about it. It was sort of the whole gestalt of the tool. But again, by that time, I was probably used to Sublime's quirks and didn't want to learn new quirks, I mean, how to deal with new quirks, in the editor that is.
VS Code definitely has some quirks and takes some time getting used to but I guess it's that way with any editor.
I use Nodepad++ for most of my none programming needs and I'm used to it and have pretty well discovered all the quirks and such. It's kind of like a pair of boots/shoes once you break them in they are comfortable and going to a new pair is a PITA because you have that break in period and you know it's going to hurt.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
I'm really interested in what you found klunky about VS Code. I'm on the VS Code team and we are working on removing adoption blockers. If you can spare the time to describe what put you off the product, we'd really appreciate it. Then we can work on it and improve the experience.
To set up a task, press Ctrl-Shift-B. If you don't have any tasks defined, VS Code will show a message box saying that no task runner has been configured. Click the button at the right hand side of the message box to configure a task runner.
You'll see a drop down offering a list of different task runners. Choose the 'Others' option at the bottom. This will generate a file in the .vscode folder that shows how to configure VS Code to run an external program (e.g., python.exe).
You can modify the example that is generated for you to look like this:
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
This tells VS Code to run the python command (make sure your environment is set up to find python.exe in your path, otherwise specify the full path to python.exe as the value for the command field). The args attribute specifies that the current open file should be passed as an argument to the python command.
Save any changes you make to this file, open the python file you want to run then press Ctrl-Shift-B. This will run the task you just specified on the currently open file.
If this all works properly you should see the output from your python program in the Output window.
Give the extension a try. It is simple to setup and not only does it allow you to run your Python code from inside VS Code it allows you to debug the code too. You can place breakpoints, step through the code, inspect variables etc.
VS Code is a rich code editor that aims to support all sorts of different languages and runtimes. So there is going to be a little bit of configuration required to get it to do exactly what you want with a specific language and runtime. We're always looking for ways to make this easier though.