No editor action to jump to next error in project

[atombender]

• VSCode Version: 1.6.1

The editor action editor.action.marker.next ("Go to Next Error or Warning") only works for the current file. There seems to be no editor action for finding the next error in the project, even when the errors panel shows multiple files.

[rebornix]

assign to @alexandrudima first per git blame but I think we might already have this issue reported.

[alexdima]

fyi @jrieken @sandy081

[jrieken]

@atombender @steveluc and other subscribed to this issue: What would be the expected behaviour when you have errors but not in the current file. Would you expect to replace the current file with the 'first' file with errors or is that only expected when coming from a file with errors?

[pragmascript]

I would expect the same behaviour as "clicking" the same error in the problem panel.

[atombender]

I would expect a new tab to be opened for the erroring file. I would expect that it would marked as a preview tab, so that multiple "next error" jumps forward would replace that new tab with the next file.

There has to be a "previous error" command, too, of course.

[jrieken]

I would expect a new tab to be opened

Sure, but in which column. The same, I assume.

[atombender]

Column? As in editor split pane? The same, yes.

[jrieken]

Wrt to navigation order our plan is to use the order of the markers panel. Today F8 and the marker panels are two different components but the plan is to let them both use the same model. That means sorting and filtering will apply to F8.

1. Files are sorted by the presence of at least one error, then by their filename

2. When a filter is applied F8 only visits only markers from the filtered-view-model

Makes sense, feedback? Would you rather keep both components disconnected?

[sandy081]

@jrieken You said, we will not move F8 functionality to Problems panel. If so, Let me know if there is anything to be done in Problems panel? User can already navigate problems across files in the panel.

[jrieken]

@sandy081 you are off the hook, it already happened

[monk-time]

@jrieken I don't quite understand why this change was implemented as a total replacement of the old behavior. I can see its usefulness in projects where all files have zero problems. But as it stands now it's no longer possible to use a keyboard shortcut (F8) to navigate through the problems only in the current file, which can be very useful when working on a project where many files have unresolved problems.

I don't think I'm the only one who has gotten used to the old behavior, and to me switching to an unrelated file on F8 (with no way to limit it only to the current file) is quite jarring and disruptive. I hope you would consider adding a way to configure this or at least a pair of keyboard bindings for the old behavior.

Also see #47367 (maybe that issue can be renamed as a feature request for a setting/bindings).