From 28a2e6da086066b5dd47ebe0abf78986842d8a94 Mon Sep 17 00:00:00 2001 From: LLLichlet Date: Mon, 6 Jul 2026 19:58:46 +0800 Subject: [PATCH] Correct 'demons' to 'daemons' in LSP documentation --- docs/extensibility/language-server-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extensibility/language-server-protocol.md b/docs/extensibility/language-server-protocol.md index a3213aa1af3..34f808ed1df 100644 --- a/docs/extensibility/language-server-protocol.md +++ b/docs/extensibility/language-server-protocol.md @@ -18,7 +18,7 @@ Creating language-specific domain models are also a lot easier if a development ### Language servers -Another approach is to run the library in its own process and use inter-process communication to talk to it. The messages sent back and forth form a protocol. The language server protocol (LSP) is the product of standardizing the messages exchanged between a development tool and a language server process. Using language servers or demons is not a new or novel idea. Editors like Vim and Emacs have been doing this for some time to provide semantic auto-completion support. The goal of the LSP was to simplify these sorts of integrations and provide a useful framework for exposing language features to a variety of tools. +Another approach is to run the library in its own process and use inter-process communication to talk to it. The messages sent back and forth form a protocol. The language server protocol (LSP) is the product of standardizing the messages exchanged between a development tool and a language server process. Using language servers or daemons is not a new or novel idea. Editors like Vim and Emacs have been doing this for some time to provide semantic auto-completion support. The goal of the LSP was to simplify these sorts of integrations and provide a useful framework for exposing language features to a variety of tools. Having a common protocol allows the integration of programming language features into a development tool with minimal fuss by reusing an existing implementation of the language's domain model. A language server back-end could be written in PHP, Python, or Java and the LSP lets it be easily integrated into a variety of tools. The protocol works at a common level of abstraction so that a tool can offer rich language services without needing to fully understand the nuances specific to the underlying domain model.