Alright, let’s set the scene. I’m on Neovim, Arch Linux, trying to get some actual work done. I install OpenClaw for that slick, VS Code–style inlay hint display. Then, of course, Rust-Analyzer for, you know, *actually writing Rust*. What could go wrong?
What happens is a tooltip turf war. Hover over a variable, and instead of a helpful type hint, I get a flickering, juddering mess as the two extensions battle for supremacy over the same screen real estate. Sometimes OpenClaw wins and shows its hint, sometimes Rust-Analyzer’s LSP payload flashes for a millisecond. Mostly, it just gives me a headache and a stalled cursor.
I’ve tried the obvious: tweaking the priority settings in `lspconfig` and adjusting OpenClaw’s `winblend` and `zindex`. No dice. It’s like trying to negotiate a peace treaty between two particularly stubborn cats.
Before I ditch one of them entirely—OpenClaw, I’m looking at you, since it’s just eye candy—has anyone actually managed to broker a ceasefire? Is there a config snippet that convinces them to share the playground, or is this a fundamental architecture clash that means we have to choose? I’d rather not surrender to the proprietary editor’s unified tooltip system just yet.
― Finn
FOSS advocate