Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks::problemMatcher should highlight problems in output log and make files clickable #18369

Closed
kobalicek opened this issue Jan 10, 2017 · 5 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) tasks Task system issues

Comments

@kobalicek
Copy link

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...

@mjbvz mjbvz added tasks Task system issues feature-request Request for new features or functionality labels Jan 10, 2017
@o-lim
Copy link

o-lim commented Apr 16, 2017

👍

@dbaeumer
Copy link
Member

Support for this will come with the new terminal runner but not with the old output runner.

@o-lim
Copy link

o-lim commented Apr 25, 2017

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.

@dbaeumer
Copy link
Member

Yes, we will support to not close the terminal.

@dbaeumer
Copy link
Member

dbaeumer commented Nov 9, 2017

Dups #21928

@dbaeumer dbaeumer closed this as completed Nov 9, 2017
@dbaeumer dbaeumer added *duplicate Issue identified as a duplicate of another issue(s) and removed feature-request Request for new features or functionality labels Nov 9, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) tasks Task system issues
Projects
None yet
Development

No branches or pull requests

4 participants