https://bugs.kde.org/show_bug.cgi?id=447172
--- Comment #3 from Jonathan Rubenstein <jrub...@gmail.com> --- My initial comment was a bit of a mess, so here is one with further clarity: Because Kate's LSP Plugin maps LSP servers to syntax highlighting mode only, new languages without KSyntaxHighlighting definitions require a lot of Kate specific metadata in order to use. Some niche languages may not be worth the effort to author and maintain the editor-specific metadata for. Kate's LSP support is crippled by this dependency on KSyntaxHighlighting definitions. One of the LSP's significant benefits is plugging in a platform-independent server, which contains all of the metadata about how the language works, and can provide many editing services without any baked-in knowledge of the editor utilizing it. Minimizing the amount of Kate-only metadata required to get an LSP server running is important to its utility and convenience. I think matching on file Mode (not Highlighting)—which has file extension matching—is a good option. It's easy to create new Modes in Settings -> Open/Save -> Modes & Filetypes, you don't even have to leave Kate. Matching on file extensions defined in the LSP configuration directly would be the easiest method, but Modes themselves are just fine. Maybe this deserves a new bug because this one is already a mess. I used clang and C because it's an easy demonstration of the issue, namely the LSP server being intrinsically tied to Highlighting, instead of something better. -- You are receiving this mail because: You are watching all bug changes.
