-
-
Notifications
You must be signed in to change notification settings - Fork 192
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
Emacs Flymake: diagnostics not cleared sometimes #398
Comments
Yes, I'm still investigating that, apparently if quick-lint-js crashes (make-process) is never calling us back so we don't have a chance to disable ourselves or update the current errors, but im not 100% sure about this, what im tho is we are never taking the :panic branch, even if we crash. |
wgrr
added a commit
to wgrr/quick-lint-js
that referenced
this issue
Jul 24, 2021
This is causing diagnostics to not be cleared sometimes (see quick-lint#398), it was first introduced for developement, because restarting Flymake without changes in buffers would not delete old diagnostics, I think it's fine if we not specify this option. However I suspect this is a bug in Flymake. Signed-off-by: wagner riffel <[email protected]>
Closed
wgrr
added a commit
to wgrr/quick-lint-js
that referenced
this issue
Jul 31, 2021
This is causing diagnostics to not be cleared sometimes (see quick-lint#398), it was first introduced for developement, because restarting Flymake without changes in buffers would not delete old diagnostics, I think it's fine if we not specify this option. However I suspect this is a bug in Flymake. Signed-off-by: wagner riffel <[email protected]> (cherry picked from commit 6a223f8)
wgrr
added a commit
to wgrr/quick-lint-js
that referenced
this issue
Aug 1, 2021
This is causing diagnostics to not be cleared sometimes (see quick-lint#398), it was first introduced for developement, because restarting Flymake without changes in buffers would not delete old diagnostics, I think it's fine if we not specify this option. However I suspect this is a bug in Flymake. Signed-off-by: wagner riffel <[email protected]> (cherry picked from commit 6a223f8)
wgrr
added a commit
to wgrr/quick-lint-js
that referenced
this issue
Aug 1, 2021
This is causing diagnostics to not be cleared sometimes (see quick-lint#398), it was first introduced for developement, because restarting Flymake without changes in buffers would not delete old diagnostics, I think it's fine if we not specify this option. However I suspect this is a bug in Flymake. Signed-off-by: wagner riffel <[email protected]> (cherry picked from commit 6a223f8)
wgrr
added a commit
to wgrr/quick-lint-js
that referenced
this issue
Aug 1, 2021
This is causing diagnostics to not be cleared sometimes (see quick-lint#398), it was first introduced for developement, because restarting Flymake without changes in buffers would not delete old diagnostics, I think it's fine if we not specify this option. However I suspect this is a bug in Flymake. Signed-off-by: wagner riffel <[email protected]> (cherry picked from commit 6a223f8)
3 tasks
wgrr
added a commit
to wgrr/quick-lint-js
that referenced
this issue
Aug 11, 2021
This is causing diagnostics to not be cleared sometimes (see quick-lint#398), it was first introduced for developement, because restarting Flymake without changes in buffers would not delete old diagnostics, I think it's fine if we not specify this option. However I suspect this is a bug in Flymake. Signed-off-by: wagner riffel <[email protected]> (cherry picked from commit 6a223f8)
3 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repro:
//
//
At this point, Flymake should report no issues, but it reports an unclosed regexp literal error.
documents
The text was updated successfully, but these errors were encountered: