https://bugs.kde.org/show_bug.cgi?id=447172
Bug ID: 447172
Summary: Difficult to use LSP Semantic Tokens when LSP Client
matches Syntax Highlighting mode
Product: kate
Version: 21.12.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Enable semantic highlighting in LSP Client settings
2. Install clangd
3. Open kate/kate/kateapp.cpp
4. Change Highlighting mode to None
OBSERVED RESULT
LSP Client stops completely, no semantic highlighting is used, and of course
Kate's syntax highlighting stops as well
EXPECTED RESULT
Kate's syntax highlighting stops, LSP Client continues working, clangd semantic
highlighting is used
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.23 user edition
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
This is intentional behavior, but I believe there should be more options to
match for LSP Client than just the syntax highlighting mode.
The normal "Mode" is still "C", and I would like to be able to match against
that mode, or even better, file extensions directly.
I feel this Highlighting mode requirement makes it hard to drop in an LSP for
any language without some specific non/trivial Kate/KDE metadata setup for
KSyntaxHightlight, which I feel defeats some of the utility of LSP as a plug
and play language service for any arbitrary language.
--
You are receiving this mail because:
You are watching all bug changes.
