|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Language Server Protocol||9,578||7 days ago||229||other||HTML|
|Defines a common protocol for language servers.|
|Nvim Lspconfig||7,484||12 hours ago||35||apache-2.0||Lua|
|Quickstart configs for Nvim LSP|
|Eglot||1,926||4 days ago||77||gpl-3.0||Emacs Lisp|
|A client for Language Server Protocol servers|
|Vscode Java||1,883||3 days ago||803||epl-2.0||TypeScript|
|Java Language Support for Visual Studio Code|
|Kotlin Language Server||1,212||12 days ago||1||March 10, 2021||161||mit||Kotlin|
|Kotlin code completion, linting and more for any editor/IDE using the Language Server Protocol|
|Go Langserver||1,113||9||17||2 years ago||7||August 24, 2021||60||mit||Go|
|Go language server to add Go support to editors and other tools that use the Language Server Protocol (LSP)|
|Vim Lsp Settings||1,111||4 hours ago||71||mit||Vim Script|
|Auto configurations for Language Server for vim-lsp|
|Php Language Server||1,061||26||1||2 years ago||64||November 13, 2018||267||isc||PHP|
|PHP Implementation of the VS Code Language Server Protocol 🆚↔🖥|
|Texlab||1,042||5 hours ago||5||June 13, 2022||26||gpl-3.0||Rust|
|An implementation of the Language Server Protocol for LaTeX|
|Language Tools||1,006||168||a day ago||201||June 26, 2022||223||mit||TypeScript|
|The Svelte Language Server, and official extensions which use it|
Emacs Polyglot is the Emacs LSP client that stays out of your way:
M-x package-install RET eglot RET into Emacs 26.3+.
Now find some source file, any source file, and type
That's it. If you're lucky, this guesses the LSP program to start for the language you're using. Otherwise, it prompts you to enter one.
First, configure this repository.
(add-to-list 'package-archives '("gnu-devel" . "https://elpa.gnu.org/devel/"))
M-x package-install or
M-x package-update to install
an ELPA package from the latest upstream.
Eglot is now in Emacs's core! Upcoming Emacs 29 will have
M-x eglot built-in.
The recommended way to experiment with changes to the latest Eglot is to compile Emacs yourself.
From a development perspective, moving to core allows us to work on Eglot in tandem with other related packages already in Emacs, such as Flymake, ElDoc, Xref, Project.
This means adding or tweaking an Emacs LSP feature is a matter of submitting a single patch targetting multiple relevant packages, not just Eglot.
:core packages (Eglot included) are then released periodically
to GNU ELPA, so users of other Emacs's versions can get them via
This repository is not the development upstream anymore, but it's not dead (yet):
It may be used to start discussions.
Sometimes, it's possible the discussion or bug report will be moved
to Emacs's bug tracker. You may take the
initiative and start discussion there using
or simply sending mail to
Please the Eglot-specific bug-reporting instructions.
eglot.el file here is periodically updated to mirror
the Emacs upstream
The existing tests of
periodically updated, may be used to rehearse and validate patches
using GitHub CI infrastructure.
These are just some of the servers that
M-x eglot can use out of the
box. The full list can be consulted in the
variable, where you can easily add your own servers.
The animation shows company-mode presenting the completion
candidates to the user, but Eglot works with the built-in
completion-at-point function as well, which is usually bound to
Eglot provides template based completion if the server supports
snippet completion and yasnippet is enabled before
Eglot connects to the server. The animation shows
completion-at-point also works with
Eglot relays the diagnostics information received from the LSP server
to Emacs's Flymake, which annotates/underlines the
problematic parts of the buffer. The information is shared with the
ElDoc system, meaning that the commands
eldoc-doc-buffer (the latter bound to
C-h-. for convenience) show
diagnostics along with other documentation under point.
Flymake provides other convenient ways to view and manage diagnostic errors. These are described in its manual.
When Eglot manages a buffer, it disables pre-existing Flymake
backends. See variable
eglot-stay-out-of to change that.
The LSP server may provide code actions, for example, to fix a
diagnostic error or to suggest refactoring edits. The commands are
frequently associating with Flymake diagnostic annotations, so that
left-clicking them shows a menu. Additionally, the command
eglot-code-actions asks the server for any code spanning a given
Sometimes, these code actions are initiated by the server. See
eglot-confirm-server-initiated-edits to control that behaviour.
Here, too, the LSP server's view of a given symbol or function
signature is relayed to the ElDoc system. The commands
eldoc-doc-buffer commands access that information.
There are customization variables to help adjust ElDoc's
liberal use of the lower "echo area", among other options. If you
still find the solicitous nature of this LSP feature too distracing,
you can use
eglot-ignored-server-capabilities to turn it off.
M-x eglot-rename RET to rename the symbol at point.
To jump to the definition of a symbol, use the built-in
xref-find-definitions command, which is bound to
Eglot here relies on Emacs' built-in functionality as well.
xref-find-references is bound to
M-?. Additionally, Eglot
provides the following similar commands:
Around May 2018, I wrote a comparison of Eglot to
was discussed with its then-maintainer. That mode has since been
refactored/rewritten and now
purports to support
a lot of features that differentiated Eglot from it. It may now be
very different or very similar to Eglot, or even sing with the birds
in the trees, so go check it out. That said, here's the
original comparison, which I will not be updating any more.
"Eglot is considerably less code and hassle than lsp-mode.el. In most cases, there's nothing to configure. It's a minimalist approach focused on user experience and performance.
The single most visible difference is the friendly entry point
M-x eglot, not
M-x eglot-<language>. Also, there are no
eglot-<language> extra packages.
There's no "whitelisting" or "blacklisting" directories to
M-x eglot starts servers to handle file of a major
mode inside a specific project, using Emacs's built-in
library to discover projects. Then it automatically detects current
and future opened files under that project and syncs with server;
Easy way to quit/restart a server, just middle/right click on the connection name;
Pretty interactive mode-line section for live tracking of server communication;
Automatically restarts frequently crashing servers;
Slow-to-start servers start asynchronously in the background;
Server-initiated edits are confirmed with the user;
Diagnostics work out-of-the-box (no
Smoother/more responsive (read below).
Under the hood:
textDocument/hoveruntil server is ready.
textDocument/didChangefor groups of edits, not one per each tiny change.
markdown-mode, if you happen to have these installed.
Eglot is subject to the same copyright assignment
Any legally significant contributions can only be merged after the author has completed their paperwork. Please ask for the request form, and we'll send it to you.