| Summary: | Kate with rust-analyzer messes up code badly on save | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | kimimaru |
| Component: | application | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | waqar.17a |
| Priority: | NOR | ||
| Version First Reported In: | 25.04.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | A video demonstrating the bug with improperly formatting code | ||
|
Description
kimimaru
2025-05-25 09:55:02 UTC
1. Is LSPClient -> Client Settings -> Format on save/typing off? 2. Is the "Formatting" plugin enabled? 3. What happens if you run rustfmt from the cmdline? When LSPClient -> Client Settings -> Format on save/typing is off, it behaves as if running rustfmt manually. The Formatting plugin is on. I noticed the problem occurs so long as Format on save/typing is on during the entire Kate session. When turning it off, I have to restart Kate entirely to disable the behavior - even restarting the LSP server doesn't work. Then I suggest turning either formatting plugin off or disabling formatting on save in lsp plugin. They can clash, and the resulting behavior is undefined.(In reply to kimimaru from comment #2) |