-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Configure task runner should only open output if autodetection fails or provides output. #3304
Labels
Milestone
Comments
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
tasks
Task system issues
labels
Feb 23, 2016
👍 |
+1 |
ping @dbaeumer so you are aware of the change |
Reopening and reverting the commit. The problem here is that if the autodetection fails output is shown in the console. Now the user is blind. |
dbaeumer
changed the title
Configure task runner should not open output
Configure task runner should only open output if autodetection fails or provides output.
Feb 29, 2016
dbaeumer
added a commit
that referenced
this issue
Mar 17, 2016
… friendly) and #3304 (Configure task runner should only open output if autodetection fails or provides output.)
Fixed. |
@isidorn let me know if you are more happy with the new implementation. |
@dbaeumer looks good to me |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
#3159
Configure task runner command reveals task output, it should not since there is no new output.
The text was updated successfully, but these errors were encountered: