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

Question: Rust analyzer all features #640

Open
klautcomputing opened this issue Feb 15, 2025 · 2 comments · May be fixed by #641
Open

Question: Rust analyzer all features #640

klautcomputing opened this issue Feb 15, 2025 · 2 comments · May be fixed by #641

Comments

@klautcomputing
Copy link

klautcomputing commented Feb 15, 2025

I am trying to get my config ported over to nvf but I am struggling to get rust-analyzer configured correctly. I am working in a project with many feature flags which I would like to be enabled.

          rust = {
            enable = true;
            format.enable = true;
            lsp = {
              enable = true;
              opts = ''
                ['rust-analyzer'] = {
                  cargo = { allFeatures = true },
                  checkOnSave = true,
                  check = {
                    enable = true,
                    command = 'clippy',
                    features = 'all',
                  },
                  procMacro = {
                    enable = true,
                  },
                },
              '';
            };
            treesitter.enable = true;
            crates = {
              enable = true;
              codeActions = true;
            };
          };

This is the relevant block in my nvf config. The rust-analyzer part is copied from my lua config, where it worked fine. So I am trying to figure out what's wrong here...

Any help would be appreciated!

@horriblename horriblename linked a pull request Feb 15, 2025 that will close this issue
@horriblename
Copy link
Collaborator

fixed in #641

in the meantime, rustaceanvim supports project local lsp settings via .vscode/settings.json

@klautcomputing
Copy link
Author

Thanks that was quick! I was wondering what I did wrong there...

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

Successfully merging a pull request may close this issue.

2 participants