https://bugs.kde.org/show_bug.cgi?id=492061
--- Comment #2 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- (In reply to Waqar Ahmed from comment #1) > You can ignore that error, rust-analyzer continues to work correctly despite > what it says. If the error is expected, could the plugin be configured to accept this specific error response when starting the server? My issue isn't about the message in the LSP output, it's that it forces open the Output tab (and flashes the tab at you) because it thinks there's some serious problem you need to deal with. I think fixing that would be a good QoL improvement. > If we do it, then Kate will open a server for every new root it finds, which > is a disaster. If you want to do it, change your lsp settings and specify > the following for rust-analyzer: > > "rootIndicationFileNames": ["Cargo.lock", "Cargo.toml"], I don't immediately see why this is so bad: is the idea that if I open multiple projects in a single Kate session, one rust-analyzer instance should be sufficient to handle all of them as if they were one big project? Does rust-analyzer's "project awareness" have any benefits that we're forgoing by doing it this way? > I would suggest taking this up with rust-analyzer, it should be able to > discover the root on its own (and it does). I will file a bug on that end too and see what they make of it, thanks! -- You are receiving this mail because: You are watching all bug changes.
