This article explains the Language Server Protocol (LSP), which was introduced by Microsoft to solve the complexity of integrating language-specific features in code editors. LSP separates language servers from code editors, providing interoperability through a defined set of standard messages using JSON-RPC. The article also covers how LSP works and provides an example with the Go programming language.
Justin Barclay, a software engineer, shares his journey of turning the Emacs text editor into a feature-rich Integrated Development Environment (IDE). He discusses the enhancements made to Emacs 29, such as syntax highlighting, code diagnostics, and IntelliSense capabilities.
Vanilla Emacs# You could go minimal and use lsp-mode as it is without external packages with the built-in flymake and completion-at-point or you could install the following extensions for better experience:
lsp-ui for fancy sideline, popup documentation, VScode-like peek UI, etc. flycheck if you prefer the more popular flycheck over renewed flymake. lsp-mode will automatically pick it up. company-mode for completion popups. lsp-treemacs for various tree based UI controls (symbols, errors overview, call hierarchy, etc.) helm-lsp provides on type completion alternative of xref-apropos using helm. lsp-ivy provides on type completion alternative of xref-apropos using ivy. dap-mode if your language is supported by the debugger.
