We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://www.flycheck.org/en/latest/user/error-interaction.html says:
Visible compilation buffers such as buffers from M-x compile, M-x grep, etc. still take precedence over Flycheck’s errors.
I take "visible" to mean that the buffer has to be visible on the screen, as opposed to merely existing and being buried.
However next-error invariable uses *compilation* if it exists, even if buried.
next-error
*compilation*
This is with flycheck-standard-error-navigation set to t.
flycheck-standard-error-navigation
t
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://www.flycheck.org/en/latest/user/error-interaction.html says:
I take "visible" to mean that the buffer has to be visible on the screen, as opposed to merely existing and being buried.
However
next-error
invariable uses*compilation*
if it exists, even if buried.This is with
flycheck-standard-error-navigation
set tot
.The text was updated successfully, but these errors were encountered: