Description
What's the point in creating a whole new Editor (LSP) section?
INHO it would have been more effective to add an "LSP" sub-element to the existing Editor section
The new LSP based editor has nothing to do with the old one. That's why we added a separate preference section. It's a complete new approach. See also this comment here.
Most of the editor settings is done via configuration files. That's why users may miss many entries in the CDT preference pages.
All code formatting settings are now done via the.clang-formatfile in the project. This is because the language server does the formatting and not Eclipse CDT anymore:
I hope the std Editor "Syntax Coloring" will easily find its way into the Editor (LSP) tab.
The editor "Syntax Coloring" is done via themes. They are defined via css files as described above. Currently the themes cannot be edited (see eclipse-tm4e/tm4e#98). Due to limited developer resources this has not been implemented yet. I'll create an issue on that.
The advantage of doing preferences via (mostly standardized) config files is that these projects can be edited in every modern C/C++ editor without the purpose to re-establishing their preferences. For example in Visual Studio Code.
Modern C/C++ editors use language server backed editors because it's much easier to support new language features/standards. Only the language server must be updated. Then the editor supports for example new language standards like C++ 23.
Originally posted by @ghentschke in #455
Since the LSP based editor uses TextMate themes for "Syntax Coloring" the user has no possibility to modify these themes because it's not supported by TextMate. See this TextMate issue eclipse-tm4e/tm4e#98