question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Go to next error/warning/info

See original GitHub issue

I’d love a feature where I could go to the next error in the file I’m in, or in the entire project, but not the next warning/info marker. Currently I have these shortcuts available:

  • editor.action.marker.next
  • editor.action.marker.nextInFiles
  • editor.action.marker.prev
  • editor.action.marker.prevInFiles

I think it’d make a lot of sense to expose similar shortcuts for going to the next error, or the next warning, or the next info, but as separate groups.

Example use case: I have a spell checker and a linter enabled for my project. The linter produces both warnings and errors, and the spell checker produces info markers. I care mostly about linter errors and compiler errors, and when those are fixed I care about spelling errors.

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:25
  • Comments:11

github_iconTop GitHub Comments

8reactions
mellestercommented, Feb 21, 2021

It would be nice if we could define something like this

    {
        "key": "f4",
        "command": "editor.action.marker.next",
        "args": "Error|Warn"
    }

And it would skip the Info markers

7reactions
yy0931commented, May 19, 2022

I made a VSCode extension because I’ve also been having trouble with this. https://marketplace.visualstudio.com/items?itemName=yy0931.go-to-next-error

Read more comments on GitHub >

github_iconTop Results From Across the Web

Visual Studio Code go to next error or warning, but not to info
In my testing severity navigates to errors, and not infos when you press F8 (and may be the new default). position visits all...
Read more >
Visual Studio Code: Use keyboard to jump to first error from ...
I am aware that one could jump to the next problem with F8 or Ctrl + Shift + M , but that does...
Read more >
Analyze code issues in design time - ReSharper - JetBrains
Right-click the status indicator and choose Go to Next/Previous Error/Warning/Suggestion — these commands will help you navigate between ...
Read more >
Visual Studio Code Key Bindings
You can open this editor by going to the menu under File > Preferences > Keyboard Shortcuts. ... Go to Next Error or...
Read more >
Excel VBA Error Handling - All You Need to Know!
No matter how experienced you're with VBA coding, errors are always going to be ... When you use 'On Error Resume Next' in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found