rust-analyzer as an LSP in kate stopped working

[Asqiir]

This regression was introduced in #191 which updated kate from 23.08 to 24.05. I believe it was this specific commit from the kate project.

I could fix this locally with adding the old version of rust-analyzer as a custom setting.

1. Can somebody on a different setup check whether they can reproduce this?
2. If so, can we figure out (with reasonable effort), what the root cause is?
3. If not, should we add my hacky patch to plasma-manager's kate?

[Asqiir]

and Somebody On Reddit has the same issue

[ada4a]

hi, it seems like you forgot to close this issue

[Asqiir]

@ugur-a I was hoping for somebody else to confirm (or reject) whether they have the same issue: If it's just me, we can close it. If it's a common issue, I would like to know to figure out a good fix.

[ada4a]

Oh god sorry I totally misread this. So:

1. I created a small config (literally just the rust-analyzer setup), and it does indeed fail to find the workspace when I don't have "rootIndicationFileNames" = ["Cargo.lock" "Cargo.toml"]; set.
2. Unfortunately, I have no idea what the root cause could be. But the Reddit post's OP didn't say anything about plasma-manager (or home-manager in general), so nothing would indicate that it's the one to blame?
3. Whatever that would be, I'd say your workaround couldn't hurt?

[Asqiir]

The root cause is that they removed these rootIndicatorFilenames from upstream kate. And if this is a common issue, somebody (I) should probably file a bug report.