You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. install servers for languages of your choice. Below are examples for Python (with [pyls](https://github.com/palantir/python-language-server)) and R (with [languageserver](https://github.com/REditorSupport/languageserver)):
94
-
95
-
```bash
96
-
pip install python-language-server[all]
97
-
```
98
-
99
-
```bash
100
-
R -e 'install.packages("languageserver")'
101
-
```
89
+
1. install and enable the server extension:
102
90
103
-
For the full list of language servers see the [Microsoft's list](https://microsoft.github.io/language-server-protocol/implementors/servers/); it may also be good to visit the repository of each server as many provide some additional configuration options.
3. install LSP servers for languages of your choice; for example, for Python ([pyls](https://github.com/palantir/python-language-server)) and R ([languageserver](https://github.com/REditorSupport/languageserver)) servers, use:
where `path_to_jupyterlab_staging` is the location of JupyterLab staging directory. Here are example locations on Ubuntu:
109
+
Please see our full list of [supported language servers](./py_src/jupyter_lsp/README.md#installing-language-servers) which includes installation hints for the common package managers (npm/pip/conda).
110
+
In general, any LSP server from the [Microsoft's list](https://microsoft.github.io/language-server-protocol/implementors/servers/) should work after [some additional configuration](./py_src/jupyter_lsp/CONTRIBUTING.md#specs).
125
111
126
-
- if you use pyenv it should be in `~/.pyenv/versions/YOUR_VERSION_OR_VENV/share/jupyter/lab/staging/`
127
-
- if you use local installation, it might be in `~/.local/lib/python3.6/site-packages/jupyterlab/staging/` (where instead of python3.6 you should use your Python3 version having JupyterLab installed)
112
+
Note: it may be worth visiting the repository of each server you install as many provide additional configuration options.
128
113
129
-
5. (Optional) to enable opening files outside of the root directory (the place where you start JupyterLab),
130
-
create `.lsp_symlink` and symlink your `home`, `usr`, or any other location which includes the files that you wish to make possible to open in there:
114
+
4. (Optional) to enable opening files outside of the root directory (the place where you start JupyterLab),
115
+
create `.lsp_symlink` and symlink your `home`, or any other location which includes the files that you wish to make possible to open in there:
131
116
132
-
```bash
133
-
mkdir .lsp_symlink
134
-
cd .lsp_symlink
135
-
ln -s /home home
136
-
ln -s /usr usr
137
-
```
117
+
```bash
118
+
mkdir .lsp_symlink
119
+
cd .lsp_symlink
120
+
ln -s /home home
121
+
```
138
122
139
-
If your user does not have sufficient permissions to traverse the entire path, you will not be able to open the file. A more detailed guide on symlinking (written for a related jupyterlab-go-to-definition extension) is available [here](https://github.com/krassowski/jupyterlab-go-to-definition/blob/master/README.md#which-directories-to-symlink).
123
+
If your user does not have sufficient permissions to traverse the entire path, you will not be able to open the file. A more detailed guide on symlinking (written for a related jupyterlab-go-to-definition extension) is available [here](https://github.com/krassowski/jupyterlab-go-to-definition/blob/master/README.md#which-directories-to-symlink).
0 commit comments