language-server-protocol

I've implemented a LSP server (for Slint - https://slint.dev) and I agree with this article. The paradox is that it was meant to avoid to write language support for each editor. Yet, if you want to support vscode you must create a specific extension for it and can't just have a language client. The article mention the configuration problem, but I'd add the problem that Microsoft refuses to specify a way for the server to tell the client what are the config options so that the client can show some kind UI showing the possible configuration options with a description of what they do. https://github.com/microsoft/language-server-protocol/issues...

For earlier archaeology see [19]. It seems to me people had started coding extensions in VS Code without giving any real thought to the question, so the default choice inherited from the language was UTF-16. [19]: https://github.com/microsoft/language-server-protocol/issues...

There was a lengthy discussion on this [1]. UTF-16 was used because it was convenient: it's what Microsoft API's and JavaScript already use (the latter being the language VS Code is written in). [1] https://github.com/microsoft/language-server-protocol/issues...

I have been coding in Rust now for almost a year and, coming from other programming languages I always missed having a way to quickly run tests in VSCode. The `rustAnalyzer.run` option never worked very well for me, as it didn't seem to work consistently and one of the things I really wanted to work was the ability to execute the last test over and over again. So I ended up scratching my own itch and I just recently put together this extension that allows you to trigger the test that you have the cursor in by quickly pressing a keystroke. On top of that, and maybe the the most useful feature, is that it remembers which test you last executed, so you can just press another keystroke to re-trigger that test. So let’s say you’re working on a test and you need to go back and forth into the code being tested, you can avoid to do so with that k

>IntelliJ helps you with things like "extract parameter" or "inline function", but I wanted to do stuff like... In the same vein as the developments around LSP, TreeSitter, etc. I had the idea that one could create a scripting language dedicated to refactors. The language would make it simple to talk about the AST of your programming language and provide simple primitives for safely transforming it. Doing this in a language-agnostic way is pretty difficult, though. There seems to be some discussion among the LSP folks here (https://github.com/microsoft/language-server-protocol/issues...) but no resolution. It's worth thinking about!

Yup, code points are the way to go. The LSP is a great example of what happens otherwise [1]. The LSP authors made the controversial decision to sync documents using line/columns and UTF-16 code unit offsets rather than relying on code points. I fear they dug the hole deeper by expanding the set of supported encodings to UTF-8 and 32 rather than standardizing on code points. I can only hope this is treated as a stop gap solution and a proper switch to code points happens in the next major revision. It's not immediately obvious, but line/columns are not a good synchronization method either. Unicode has their own definition of what constitutes a line terminator [2], but different programming languages and environments might have their own definition. [1] https://github.com/microsoft/language-server-protocol/issues... [2] https://en.wikipedi

> But this seems to be a VSCode issue. That’s a protocol issue! While LSP has a method to report a transient (edge triggered) error, it doesn’t have a way to report a persistent (level triggered) status. And to solve configuration problem, you really want a “status” concept - you need an LSP health indicator which is either red or green, and which you can click on to get info about what the server thinks the project is. There’s no such feature in LSP at the moment. https://github.com/microsoft/language-server-protocol/issues...

tree-sitter is a phenomenal project i’m doing a git-related project myself and use it to generate symbols for source code if you’re into it too, i recommend also checking out LSIF: https://github.com/Microsoft/language-server-protocol/blob/m...

UTF-16 was always a mistake[1]. Good riddance. Time to get it out of LSP specification[2] as well. [1] http://utf8everywhere.org/ [2] https://github.com/microsoft/language-server-protocol/issues...

A source for LSP growing out of OmniSharp? Interestingly I'm not finding much. This isn't a totally accurate history but it's close enough: https://blog.logrocket.com/how-to-use-the-language-server-pr... The original project was at https://github.com/nosami/Omnisharp (see https://news.ycombinator.com/item?id=6006954). But over time it was split into several repos. The history article above says that OmniSharp started out on Roslyn, but actually it originally used NRefactory. The old server is here: https://github.com/OmniSharp/omnisharp-server EDIT: Oh, just found https://github.com/microsoft/language-server-protocol/wiki/P... . This cites OmniSharp and also the TypeScript language server.

I wish they would provide a machine-readable version of the specification: https://github.com/microsoft/language-server-protocol/issues... Well that and use utf-8 string indexing (which is easier for every other language than javascript): https://github.com/microsoft/language-server-protocol/issues...

It looks like this is blocked upstream by the language server protocol not passing the current selection for hover requests [0]. 0: https://github.com/microsoft/language-server-protocol/issues...

"The Emacs and Vim ... are outclassed by modern IDE" Outclassed in what way? Have you looked at LSP[1] and its support in Emacs[2], for instance? That's not to mention things like SLIME and paredit for Lispy languages, or the integration of the rest of the Emacs ecosystem in to your development environment, the ability to develop and configure all these development tools in Lisp instead of being forced to switch to some other language, etc. [1] - https://github.com/Microsoft/language-server-protocol/ [2] - https://github.com/emacs-lsp/lsp-mode/

I had the sense it was on the tip of your tongue since the way you described it matched to a T, but I decided to flesh it out for folks who hadn't heard of LSPs. :) You're right, at this moment, the LSP is circumscribed in that it doesn't expose the AST (even though it could) which means one is limited to the capabilities it does expose. The claim is that the goal is parity across languages and exposing the ASTs is contrary to this [1]. I'm hoping this philosophy is challenged. In the mean time one might have to rely on languages themselves exposing their ASTs, eg. Python is able to expose its ast (via the ast module). So yes, right now one wouldn't be able to write say an IntelliJ IDEA type IDE based off a language server alone -- one wouldd have to be able to create the AST oneself. [1] https://github.com/Microsoft/language-server-proto