I get no diagnostics at all

[augustocdias]

I'm trying to configure bacon for days and I simply can't get any diagnostic from it:

I configured it like this:

        vim.lsp.enable('bacon_ls')
        vim.lsp.config('bacon_ls', {
            on_attach = lsp_utils.on_attach,
            capabilities = lsp_utils.capabilities(),
            init_options = {
                useBaconBackend = false,
                updateOnSave = true,
                updateOnChange = true,
                updateOnSaveWaitMillis = 1000,
            },
        })

I have a .nvim.lua config to disable rust-analyzer diagnostics as specified in the docs from bacon:

vim.g.rustaceanvim = vim.tbl_deep_extend('force', vim.g.rustaceanvim, {
    server = {
        settings = {
            ['rust-analyzer'] = {
                diagnostics = {
                    enable = false,
                },
                checkOnSave = {
                    enable = false,
                },
                cargo = {
                    target = 'x86_64-pc-windows-gnu',
                    features = { 'use-codebase-lib' },
                },
            },
        },
    },
})

I see bacon-ls is running but I get no diagnostic at all. What am I doing wrong?

[crisidev]

Can you run RUST_LOG=debug nvim myfile.rs? This will create a log file in the current directory that might shed some light on what is going on..

Are you by any chance on a recent nightly of neovim? I noticed that in the last two weeks, nightly doesn't receive notifications for diagnostics even if bacon-ls sent them, and I haven't had time to figure out what's going on and I switched to the latest stable for the time being.

[crisidev]

After looking the logs, I think what is happening is that cargo clippy doesn't complete cleanly because of the --all-targets and thus nothing is sent to the editor :(

You can, however, setup bacon-ls to use a different cargo command arguments using the cargoCommandArgs argument to the init_options and remove the --all-targets. This is not great, I am sorry :)

[augustocdias]

I will try that. I don't mind using it. Thanks

[crisidev]

Here is the default: https://github.com/crisidev/bacon-ls/blob/main/src/lib.rs#L33

If this doesn't work, I'll spend some time debugging it :)

[augustocdias]

I couldn't still make it work :(

This is how I set it up:

        vim.lsp.config('bacon_ls', {
            init_options = {
                useBaconBackend = false,
                updateOnSave = true,
                updateOnChange = true,
                updateOnSaveWaitMillis = 1000,
                cargoCommandArgs = 'clippy --target x86_64-pc-windows-msvc --tests --feature use-codebase-lib --all-targets --message-format json-diagnostic-rendered-ansi',
            },
        })

[crisidev]

Are you running bacon-ls on windows? Also, can you try to disable updateOnChange? That setting is a big hack, which copies the source folder to /tmp on demand and its pretty brittle.

[tmontaigu]

I also have the same problem, the default '--all-features / --all-targets' makes cargo try to compile code that is not compilable on my machine.

Modifying the init_options works, and actually the name of the option is cargoCommandArguments.

However I think it should be a setting like cago.features or cargo.buildScripts.enable are for rust-analyzer, it could make the integration with things like codesettings a bit easier