inspector71 wrote: ↑
03 Aug 2022 05:30
pjj wrote: ↑
02 Aug 2022 09:18
I suppose you're referring to Language Server Protocol (LSP), which has been implemented already and is very helpful indeed.
That's the one
You have used it?
I'm not really sure what it is. Maybe I've misinterpreted or missed something.
Yes, I do use LSP binding for three Web languages (JS, CSS, PHP), mainly as static analyzers
. In other words, they help immediately find grammar and syntax mistakes in my scripts/stylesheets.
What is the Language Server Protocol?
Adding features like auto complete, go to definition, or documentation on hover for a programming language takes significant effort. Traditionally this work had to be repeated for each development tool, as each tool provides different APIs for implementing the same feature.
A Language Server is meant to provide the language-specific smarts and communicate with development tools over a protocol that enables inter-process communication.
The idea behind the Language Server Protocol (LSP) is to standardize the protocol for how such servers and development tools communicate. This way, a single Language Server can be re-used in multiple development tools, which in turn can support multiple languages with minimal effort.
LSP is a win for both language providers and tooling vendors!
If I understand it correctly, RJ TE does not use LSP for syntax highlighting at all, hence a series of our back-and-forths in this thread
Of course resting solely
on LSP with respect to syntax highlighting would mean that everybody would need to install and use LSP to get their code properly highlighted; on the other hand I'd love to see LSP used more extensively in RJ TE!
(Yes, if regex rules were just a backup solution, we'd discuss them anyway. But with code highlighting done via LSP we would get the newest CSS bits [or JS, or PHP, etc.] sooner, simply by updating our LSP code.)