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

Jump to next error capability. #282

Open
seanparsons opened this issue Oct 15, 2018 · 5 comments
Open

Jump to next error capability. #282

seanparsons opened this issue Oct 15, 2018 · 5 comments

Comments

@seanparsons
Copy link

Something that I keep finding myself needing is the ability to just jump to the next error.

The flow being:

  1. Make a bunch of changes.
  2. Potentially see an error from webpack or similar.
  3. Press key combo to jump to next error.
  4. Fix problem.
  5. Goto 3.
@josteink
Copy link
Collaborator

I concur.

Not sure it's an exact duplicate, but this seems somewhat related to #61.

@seanparsons seanparsons changed the title Just to next error capability. Jump to next error capability. Oct 19, 2018
@ananthakumaran
Copy link
Owner

is this within a buffer or across files? Within a buffer flycheck already provides commands to navigate errors. For references/project-errors you could use n, p or next-error

@seanparsons
Copy link
Author

@ananthakumaran Well within a buffer, but across files.

@ananthakumaran
Copy link
Owner

does flycheck-next-error solve your issue?

@seanparsons
Copy link
Author

@ananthakumaran No and potentially connected if I open the flycheck error list it's empty when tide-project-errors has errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants