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.

Sign up for GitHub

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

Jump to bottom

Tasks: reveal: always / never / silent not a clear distinction #29566

Closed
isidorn opened this issue Jun 27, 2017 · 3 comments
Closed

Tasks: reveal: always / never / silent not a clear distinction #29566

isidorn opened this issue Jun 27, 2017 · 3 comments
Assignees
@alexr00
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code tasks Task system issues
Milestone
Backlog

Comments

@isidorn
Copy link
Contributor

isidorn commented Jun 27, 2017

Refs: #29442

I tried this out and I do not really see the difference between never and silent.
We should align here with debug which is: never, always and firstTime

screen shot 2017-06-27 at 12 27 58
@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug tasks Task system issues labels Jun 27, 2017
@dbaeumer
Copy link
Member

Two things to do: use enum descriptions to improve this. Silent needs a problem matcher. If a task as one attached it will not reveal. If none is attach it will.

@dbaeumer dbaeumer added this to the July 2017 milestone Jun 29, 2017
@dbaeumer dbaeumer modified the milestones: August 2017, July 2017 Jul 10, 2017
@dbaeumer dbaeumer added feature-request Request for new features or functionality and removed bug Issue identified by VS Code Team member as probable bug labels Aug 28, 2017
@dbaeumer dbaeumer modified the milestones: Backlog, August 2017 Aug 28, 2017
@dbaeumer
Copy link
Member

Added enum descriptions. Will keep the item as a FR for the firstTime. But I never had this request so far.

capture
feat

@alexr00 alexr00 assigned alexr00 and unassigned dbaeumer Oct 7, 2019
@alexr00 alexr00 added the *out-of-scope Posted issue is not in scope of VS Code label Oct 9, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 9, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexr00 alexr00

Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code tasks Task system issues
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@isidorn @dbaeumer @alexr00