The 'Jump to definition' doesn't work properly inside the folder.
See original GitHub issueDescription
The ‘Jump to definition’ doesn’t work properly inside the folder.
Reproduce
- make a new directory named
test_lsp
and go into it. - create a new Python file named
test_func.py
. - create a new Notebook file named
Untitled.ipynb
. - when I try to jump to
bark
definition, it failed with aNo jump targets found
error message.
Expected behavior
It should be jumped to test_func.py
.
Context
- Operating System and version: CentOS 7
- Browser and version: Chrome 87.0.4280.141
- JupyterLab version: 2.2.9
- @krassowski/jupyterlab-lsp@2.1.2
- jupyter-lsp==0.9.3
- python-language-server[all]==0.36.2
Required: installed server extensions
Paste the output from running `jupyter server extension list` (JupyterLab >= 3) or `jupyter serverextension list` (JupyterLab < 3) from the command line here. You may want to sanitize the paths in the output.config dir: /root/.jupyter jupyterlab_git enabled - Validating… jupyterlab_git 0.22.2 OK jupyterlab_code_formatter enabled - Validating… jupyterlab_code_formatter OK jupyter_archive enabled - Validating… jupyter_archive OK jupyter_conda enabled - Validating… jupyter_conda 3.4.1 OK config dir: /opt/conda/etc/jupyter jupyter_lsp enabled - Validating… jupyter_lsp 0.9.3 OK jupyter_conda enabled - Validating… jupyter_conda 3.4.1 OK jupyterlab enabled - Validating… jupyterlab 2.2.9 OK jupyterlab_git enabled - Validating… jupyterlab_git 0.22.2 OK nbdime enabled - Validating… nbdime 2.1.0 OK nbresuse enabled - Validating… nbresuse OK
Required: installed lab extensions
Paste the output from running `jupyter labextension list` from the command line here. You may want to sanitize the paths in the output.JupyterLab v2.2.9 Known labextensions: app dir: /opt/conda/share/jupyter/lab @arbennett/base16-gruvbox-dark v0.1.3 enabled OK @arbennett/base16-gruvbox-light v0.1.3 enabled OK @arbennett/base16-mexico-light v0.1.3 enabled OK @arbennett/base16-monokai v0.1.3 enabled OK @arbennett/base16-one-dark v0.1.3 enabled OK @arbennett/base16-outrun v0.1.3 enabled OK @arbennett/base16-solarized-dark v0.1.3 enabled OK @arbennett/base16-solarized-light v0.1.3 enabled OK @arbennett/base16-summerfruit-light v0.1.3 enabled OK @hadim/jupyter-archive v0.7.0 enabled OK @jupyter-widgets/jupyterlab-manager v2.0.0 enabled OK @jupyterlab/git v0.22.2 enabled OK @jupyterlab/toc v4.0.0 enabled OK @karosc/jupyterlab_dracula v2.0.3 enabled OK @krassowski/jupyterlab-lsp v2.1.2 enabled OK @krassowski/jupyterlab_go_to_definition v1.0.0 enabled OK @mohirio/jupyterlab-horizon-theme v2.0.0 enabled OK @ryantam626/jupyterlab_code_formatter v1.3.6 enabled OK @telamonian/theme-darcula v2.0.0 enabled OK @yeebc/jupyterlab_neon_theme v2.0.1 enabled OK jupyterlab-execute-time v1.0.0 enabled OK jupyterlab-plotly v4.12.0 enabled OK jupyterlab-python-file v0.4.0 enabled OK jupyterlab-system-monitor v0.6.0 enabled OK jupyterlab-tailwind-theme v0.4.4 enabled OK jupyterlab-theme-solarized-dark v1.0.2 enabled OK jupyterlab-topbar-extension v0.5.0 enabled OK jupyterlab-topbar-text v0.5.1 enabled OK jupyterlab_conda v2.2.4 enabled OK jupyterlab_filetree v0.2.2 enabled OK jupyterlab_theme_onedark v1.0.2 enabled OK nbdime-jupyterlab v2.0.1 enabled OK
Troubleshoot Output
Paste the output from running `jupyter troubleshoot` from the command line here. You may want to sanitize the paths in the output.
Command Line Output
Paste the output from your command line running `jupyter lab` here, use `--debug` if possible.
Browser Output (recommended for all interface issues)
Paste the output from your browser JavaScript console replacing the text in here.To learn how to open the developer tools in your browser: https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools#How_to_open_the_devtools_in_your_browser If too many messages accumulated after many hours of working in JupyterLab, consider refreshing the window and then reproducing the bug to reduce the noise in the logs.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top GitHub Comments
Let’s keep it open for reference.
@krassowski May I close this issue?