Skip to content

Use flycheck to manage error and warning overlays #821

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

Closed
4 tasks
gracjan opened this issue Aug 22, 2015 · 1 comment
Closed
4 tasks

Use flycheck to manage error and warning overlays #821

gracjan opened this issue Aug 22, 2015 · 1 comment

Comments

@gracjan
Copy link
Contributor

gracjan commented Aug 22, 2015

flycheck has achieved status of emacs standard for on-fligh error and warning reporting. It provides visually apealing indicators, infrastructure to handle more information, keybindings and user interface. There are plans to expand the functionality to provide fixing behavior.

There is no need to reimplement all of the functionality.

Tasks to do:

  • make haskell-mode depend on flycheck
  • remove current overlay functionality
  • when loading a file in interpreter gather all errors and warnings in a respective session, not that it should gather all errors and warnings for all files that are loaded in a session
  • when flycheck requests error list for a specific buffer provide it from the session

Use the :start hook in flycheck checker definition to achieve this.

@gracjan
Copy link
Contributor Author

gracjan commented Feb 22, 2016

Flycheck declared error fixups as low priority flycheck/flycheck#530, it means we need to do it ourselves.

Closing in favor of #1170.

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

1 participant