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

flycheck-mode doesn't immediately check errors when the file is opened #5

Open
IceAsteroid opened this issue Apr 15, 2024 · 1 comment

Comments

@IceAsteroid
Copy link

The first time, the file is opened, doesn't display flycheck errors in eglot.

It needs to start editing the buffer to show flycheck errors.

Flymake works fine. It shows errors when the file is first opened in eglot.

@intramurz
Copy link
Collaborator

Hi!

Could you please clarify which compiler/environment you're having trouble with? I made several small experiments: introduce an error into the code, save the file, kill the buffer, restart Emacs, open the file, look at the list of errors. I only experimented with tools that I use myself. For c/c++ (clangd) and python (pylsp), the error is detected immediately upon opening, everything is fine. Flycheck and eglot settings are default (more or less). Things are getting worse for rust, but the problem seems to be more in the design of rust (and rust-analyser) itself.

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

2 participants