I am looking for ways to create my own window to show different threads and other information in a different way. I found following is written at https://code.visualstudio.com/docs/extensions/overview
"
Debug Adapter#
VS Code implements a generic debugger UI and relies on debugger extensions and so called "debug adapters" to connect the debug UI to a real debugger or runtime. A debug adapter is a dedicated process that communicates with VS Code through the VS Code Debug Protocol and can be implemented in any language.
"
Can someone guide me if it can be done by extension or by modifying the source code of VS code itself ?
Related
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.
When we use visual studio code for flutter programming, can we restrict debugging process to user files only? and forbid the debugger from opening and debugging external libraries during the debug session?
I used the debug setting at the bottom of the visual studio main window and set it to my code only, yet, the debugger keeps branching into external files when it reaches a return statement in the widget build method.
Sample statement that causes branching into external libraries during debugging
Sample external library that joins into the debugging process
If I understood correctly, you can click a button on the bottom bar to toggle between Debug my code and Debug my code + packages'.
This button is only visible when you are in debug mode.
Apparently the behavior I described in my question was related to deep Uncaught exceptions.
Enabling All Exceptions and Uncaught Exceptions in the debug window assisted in further exploring the issue.
My issue was related to popping an out-of-context widget which caused abnormal behavior while debugging.
Coming from Eclipse, I am very used to the option to terminate the possible old and running instance of the code I'm working on. With VS Code, I instead have to select the console, press Ctrl+C, wait for the process to end and only then can I launch a new instance via Ctrl+F5 (same for debug/regular F5).
I was surprised to find no such option in VS Code, am I missing something or is this feature simply not supported ? If this is possible to configure somehow, how would I go about it ? Multiple tags because I'm not sure which part of VS Code would be responsible here. I am specifically developing in Java, if that is relevant.
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.
When reading some big open source projects' codes, it'd be pleasant if there's a view that shows the visualization result of program executing flow when debugging JavaScript. So if there're any tools like code map for debugging javascript? Like this: https://dailydotnettips.com/did-you-know-code-map-can-be-used-to-visualize-the-call-stacks-directly