You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried everything, but I'm not able to make vs-code to highlight problems in output log and make that problems clickable (click on file that will bring me to the file/line/column of the problem).
I know I can press Ctrl+Shift+M and see all problems, but that's kinda something I don't want to do if I already see the output log. I want to see something Visual Studio does when compiling the project, for example...
The text was updated successfully, but these errors were encountered:
With the new terminal runner, when the build is done it outputs a "press any key to continue" prompt, and once you hit a key all of the output disappears, which is very undesirable. Is there any plan to allow the output to remain after the build has completed? This is necessary because often the problem matchers do not capture all of the information needed to analyze a problem, and with the output gone, you would be forced to run the build again to see the full error message.
I tried everything, but I'm not able to make vs-code to highlight problems in output log and make that problems clickable (click on file that will bring me to the file/line/column of the problem).
I know I can press Ctrl+Shift+M and see all problems, but that's kinda something I don't want to do if I already see the output log. I want to see something Visual Studio does when compiling the project, for example...
The text was updated successfully, but these errors were encountered: