Commit e2982ab0 authored by Mark Nauwelaerts's avatar Mark Nauwelaerts
Browse files

lspclient: remove duplicate server configuration documentation

parent 19c26e74
......@@ -22,57 +22,8 @@
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
/*
* Some explanation here on server configuration JSON, pending such ending up
* in real user level documentation ...
*
* The default configuration in JSON format is roughly as follows;
{
"global":
{
"root": null,
},
"servers":
{
"Python":
{
"command": "python3 -m pyls --check-parent-process"
},
"C":
{
"command": "clangd -log=verbose --background-index"
},
"C++":
{
"use": "C++"
}
}
}
* (the "command" can be an array or a string, which is then split into array)
*
* From the above, the gist is presumably clear. In addition, each server
* entry object may also have an "initializationOptions" entry, which is passed
* along to the server as part of the 'initialize' method.
*
* Various stages of override/merge are applied;
* + user configuration (loaded from file) overrides (internal) default configuration
* + "lspclient" entry in projectMap overrides the above
* + the resulting "global" entry is used to supplement (not override) any server entry
*
* One server instance is used per (root, servertype) combination.
* If "root" is specified as an absolute path, then it used as-is,
* otherwise it is relative to the projectBase. If not specified and
* "rootIndicationFileNames" is an array as filenames, then a parent directory
* of current document containing such a file is selected. As a last fallback,
* the home directory is selected as "root" (or the "root" entry in "global").
* For any document, the resulting "root" then determines
* whether or not a separate instance is needed. If so, the "root" is passed
* as rootUri/rootPath.
*
* In general, it is recommended to leave root unspecified, as it is not that
* important for a server (your mileage may vary though). Fewer instances
* are obviously more efficient, and they also have a 'wider' view than
* the view of many separate instances.
/* see plugins.docbook lspclient-configuration
* for client configuration documentation
*/
#include "lspclientservermanager.h"
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment