https://bugs.kde.org/show_bug.cgi?id=473251
--- Comment #4 from doc.ev...@gmail.com --- Igor Kushnir wrote on 8/11/23 06:47: > > The error messages have different causes. Some of them are probably not > KDevelop's fault, but something's wrong on your system. The system is a clean debian bookworm system, on which kdevelop was installed for the first time a week or so ago. Which doesn't mean that there might not be a debian packaging error that might cause problems; but I have not personally done anything to the system that would cause any instability. > The kdevplatform.serialization messages is the consequence of a previous crash > of KDevelop. > "kdevplatform.util: Path::init: invalid/unsupported Path encountered: > http://clang-tidy"; => installing clang-tidy might eliminate this error. I will try that. It's a bit surprising that debian doesn't automatically install clang-tidy as a dependency when it installs kdevelop. > Hunspell configuration appears to be broken on your system. I've never knowingly used hunspell. Presumably, debian auto-installed it in a broken way as a required dependency of some other package that's installed. I'll try to figure out what is wrong and, if I can, file a packaging bug report with debian. > "/bin/sh: 1: indent: not found" => either install GNU indent or (better) > configure source formatters to match your project's code style in KDevelop > settings. I don't understand the last part of that sentence (starting with the word "configure"). But in the meantime I'll install GNU indent when I have time (probably not today). > "kdevelop.plugins.clang: Unhandled type: Dependent <dependent type>" - this > looks bad. Have you uninstalled some KDevelop language plugin? Does KDevelop > parse your source code successfully? > I have not uninstalled anything related to kdevelop. (Indeed, I don't think I've uninstalled anything at all since bookworm was installed). kdevelop does mostly seem to parse the code correctly. Every now and then (maybe once a day) I see a red message on the screen that isn't right (flagging a line as having a problem when in fact it doesn't), but the few messages that I've seen have been related to new features in C++20, and I could easily believe that they're due simply to the installed parser not being quite up to date. Thank you for your help and advice. Doc -- You are receiving this mail because: You are watching all bug changes.
