I used to use the Atom code editor and one of the features I liked about this editor was that when I executed python code it would bring up an external CMD window where I would interact with the code, if input was required, and receive the results.
I have moved to VS Code as Atom is no longer supported and I have looked on here and with Google, but I do not seem to be able to get VS Code to behave in this fashion :(
I am wondering if any of the folks on here with more experience with VS code can advise if what I am looking to do is possible or do I just have to suck it up and use the integrated terminal/output panes at the bottom of the window?
Any advise would be very much appreciated.
I have tried in the "Configure Terminal Settings" to change from Integrated to External, but this has made no difference.
Related
I am trying to make terminal interference minimal by removing element I don't need. I am beginner in programming.
I want to remove the highlighted part.:
I am using coderunner and C/C++ Compile Run. I lloked for this on google and but Code-runner: Clear previous output, it does not work for me. Also is there any way I can clear terminal automatically when running the code using ctrl+alt+N instead doing it manually?
If I can't do this in powershell is there any other shell which give this functionality?
Can anyone explain these three debug symbols on VSCode I have found on the internet?
My vs code has the one with the play icon.
All demos online on debugging have the one in the middle. How do I get that?
Also, node js debugging is installed but I think it shows as disabled, with no option I can find to enable it.
To answer your question directly [TL;DR]: you already have it if you are using the latest version of vscode. It will take you to the same view as the one on the right
If you look at the codicon libray ref the middle one you pointed out is not present.
Visual Studio Code made changes in February 2020 ref that incorporates running and debugging to be something more harmonious:
User studies revealed that new users have difficulties finding how to run their programs in VS Code. One reason is that the existing "Debugging" functionality is not something that they relate to "Running" a program. For that reason, we are making "Run" more prominent in the UI.
The main menu Debug has become the Run menu.
The Run and Debug view has become the Run view and the corresponding Activity Bar icon now shows a large "Play" icon with a small "bug" decoration.
So in other words, there is no difference. The 'Run' and 'Debug' view is synonymous and the icon reflects those changes. As they noted, the Debug view is now called the 'Run' view, but it still offers debugging and breakpoints.
There are 2 possibilities you are running into however:
The tutorials and guides you are using are out-dated (showing an outdated version of vscode)
The tutorial or guide is using an extension that offers debugging capabilities. Extensions have some control over the icon you see
The extension is for single file debugging, according to the June 2020 ref notes, vscode recommends the following:
For debug extensions that want to improve the single file debug experience by adding a "Run" and/or "Debug" button to the editor, we recommend following these guidelines for a consistent look and feel:
Contribute Run and/or Debug commands in the package.json (see Mock Debug):
Use the command titles "Run File"/"Debug File" or "Run Python File"/"Debug Python File".
Use the $(play) icon for Run and $(debug-alt-small) for Debug.
Where their codicon library was updated in June to reflect the following:
As you can see, none of them are prefixed with verbiage like 'run', but they all represent the same functionality.
Additionally, you may see this icon as well:
This represents the panel (view) where the output of your debug will go.
I'm trying to create an (ideally) all-in-one cross platform tile based map/sprite/image editor for a game engine, since the current official one is Windows only and doesn't play nicely with WINE/Mono. Instead of building one from scratch, I figured it might be easier to create an extension for Visual Studio Code, but side panes don't seem to be interactive, and I'm having trouble getting it to open an electron window.
Is this possible, or should I just build it from scratch with electron?
That won't work. Visual Studio Code is a code editor, which supports extensions that can either add functionality to the IDE itself or provide HTML content to show in an own pane. This is not enough (and not made) for a full featured editor-in-editor scenario (interaction is limited).
I've built an extension which has a graphical view of a graph (see the last image) using D3.js, with limited interaction capabilities (you can select/drag a node and pan/zoom with the mouse).
Better is probably to go level down and start with Electron (on which vscode is based). This would allow you to write any desktop application that can be written in HTML/JS.
I'm coming from a pure Windows Visual Studio programming background with little Linux experience. It seems possible to use VS Code to program in Julia, but I can't figure out how to get things set up correctly.
Does anybody have good example launch.json, tasks.json, or other files that can serve as an example to build from?
This would be a great thing to see in a detailed tutorial.
Here is how things work if you are using the Julia extension for VisualStudio Code.
The extension adds a bunch of new commands. They all start with "julia", so filtering by that string should show you everything you can do with the extension.
In terms of running Julia code, the extension offers only two options right now. First, you can execute a command to start a REPL. This will just show a default Julia prompt, and you can interact with it like you would with any other Julia REPL. The second is that there is also a command, triggered by Ctrl + Enter, to send either the current editor selection or the current editor line to this REPL.
There is currently no further integration offered by the Julia extension. We do plan to add debugger support in the future, at which point I would expect F5 to start the current file in the debugger, or something like that. But that functionality is probably a couple of months away.
I'd like to script FlexBuilder so that I can run debug or profile without having to switch to FlexBuilder and manually clicking the button (or using the key combo). Is this possible without writing an extension?
To be more specific, this is exactly what I want to do: I want to create a TextMate command that talks to FlexBuilder and makes it run the debug target for the currently selected project. TextMate already has support for interacting with Xcode in this way, and it would be great to be able to do the same with FlexBuilder.
When compiling I use Ant and have full control over that from TextMate, what I want is to be able to launch the debugger and the profiler. The command line debugger is unusable and there is no other profiler available than the one in FlexBuilder.
Since FlexBuilder essentially is an extended version of Eclipse, any tools/scripts for doing the same in Eclipse should work for FlexBuilder aswell. I couldn't find any tools like this googling it, have you considered doing away with FlexBuilder completely, there are plenty of guides for using the mxmlc (or fcsh) compilers directly from your editor.
I do not know if there is a plugin like this for Eclipse however if not you can write one as it should be easy.
If the specific command that you want to call shows up in Windows/Preferences - General/Keys, you can create a plugin that takes commands from TextMate (I do not know what protocol TextMate uses, socket or something else) and executed the specific action that is associated with the command that also appears in preferences.