Open dirkroorda opened 2 years ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Thank you for they report. I can reproduce this and will take a look at fixing this over the weekend.
@krassowski any luck with this?
Any update on this issue. I've tried the last 6 versions and all of them stall after installing the vim plugin.
Alternatively, any pointers on how to troubleshoot this ourselves then?
Thanks.
@rchavp is this still an issue with the latest version 3.6.1-1?
I gave the latest version a try, a couple of days ago. I had some kernel trouble when using my existing Python. Still jupyterlab-vim does not work, don't see clear error messages, and there is no extensions tab on the interface.
So, for the time being I give up For me personally I do not see any advantage of the Desktop version above the regular version.
Description
jupyterlab-vim
is a prebuilt extension, installable bypip install jupyterlab-vim
.Yet it does not work in the newest version of JupyterLab desktop (3.2.5-2) In the previous version of JupyterLab desktop I managed to get it working after a bit of refreshing the page.
Reproduce
%pip install jupyterlab-vim
; it will run successfullyExpected behaviour
In step 4 one should in vim normal mode, having a green block cursor, and pressing
i
ora
should bring you in insert mode with a thin cursor.This is from ordinary jupyterlab:
Vim normal mode:
after pressing
a
we are in insert mode:Observations
It happens both in the bundled Python environment (where I
%pip install jupyterlab-vim
) as in my system python environment (python 3.10.0 with jupyterlab-vim already installed).In the developer tools (View->Toggle Developer Tools) there is something irregular. See below.
Context
Troubleshoot Output
I do not do this, because it lists my system python, although I am working in the prebuilt environment! Here you see the bottom bar indicating that I'm in the prebuilt environment, but it lists `python-Levenshtein` which is a module from my system environment.Browser Output (required for interface issues after loading)
Logs (required for issues with loading, server and startup)
(I have replaced the path to my home directory by `~`).By the way: I cannot pip-uninstall modules from within the desktop app, because pip asks for confirmation, and there is no way to answer with
Y
.When uninstalling by means of
%pip --no-input uninstall jupyterlab-vim
I get an error:So I could not experiment with uninstalling and reinstalling the package again.
Screenshot: