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

"Go to Next Error or Warning" across files #20172

Closed
pragmascript opened this issue Feb 8, 2017 · 1 comment
Closed

"Go to Next Error or Warning" across files #20172

pragmascript opened this issue Feb 8, 2017 · 1 comment
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) error-list Problems view feature-request Request for new features or functionality

Comments

@pragmascript
Copy link

pragmascript commented Feb 8, 2017

There should be an option to have
"Go to Next Error or Warning" editor.action.marker.next and "Go to Previous Error or Warning" editor.action.marker.prev
work across different files so it would jump to the file of the error.
So it would work the same way as clicking the same error in the problems view.

@pragmascript pragmascript changed the title "Go to Next" across files "Go to Next Error or Warning" across files Feb 8, 2017
@Tyriar Tyriar added error-list Problems view feature-request Request for new features or functionality labels Feb 9, 2017
@sandy081 sandy081 assigned jrieken and unassigned sandy081 Feb 10, 2017
@jrieken
Copy link
Member

jrieken commented Feb 10, 2017

dupe of #14783

@jrieken jrieken closed this as completed Feb 10, 2017
@jrieken jrieken added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 10, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 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) error-list Problems view feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

4 participants