The Getting Started guide should contain all you need to get up and running with your editor of choice. However there may come a time when you will want to enable/disable certain functionality or use a different server entirely.
Wait.. there are different servers?
Yes there are!
Due to the extensible nature of Sphinx and reStructuredText, the
esbonio python package
is actually a framework for building reStructuredText language servers. It just so happens
that it also comes with a default implementation that works well for Sphinx projects (see
the section on Extending if you want to know more)
However, all that we need to know for the moment is the concept of startup modules.
A startup module is any python module (or script) that results in a running language server.
The following startup modules are included with the
esbonio python package.
The default startup module you are probably already familiar with. It is in fact just an alias for the
A “vanilla” reStructuedText language server for use with docutils projects.
A language server tailored for use with Sphinx projects.
Inspired by the way Sphinx extensions work, functionality is added to a language server through a list of python modules with each module contributing some features.
Below is the list of modules loaded by default for each of the provided servers.
In addition to the modules enabled by default, the following modules are provided and can be enabled if you wish.
Basic spell checking, with errors reported as diagnostics and corrections suggested as code actions. Currently only available for English and can be confused by reStructuredText syntax.
The bundled language servers offer some commands that can be invoked from a language client using a workspace/executeCommand request.
The bundled language servers also emit custom notifications that language clients can use to react to events happening within the server.