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

How to get diagnostics to work? #569

Open
rakanalh opened this issue Jul 3, 2024 · 0 comments
Open

How to get diagnostics to work? #569

rakanalh opened this issue Jul 3, 2024 · 0 comments

Comments

@rakanalh
Copy link

rakanalh commented Jul 3, 2024

I have added the following configuration:

   lsp-rust-analyzer-diagnostics-enable t
   lsp-diagnostic-clean-after-change t
   lsp-rust-analyzer-cargo-watch-command "clippy"
   lsp-rust-analyzer-cargo-override-command ["cargo", "clippy", "--message=format=json"]

among others in doom emacs config to get diagnostics to display about the code such as clippy errors.

Nothing really shows when using SPC c x which maps to +default/diagnostics in doom emacs which i believe uses flycheck.

Is this a feature that rustic / lsp-mode support?

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