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
When trying to run selected code in a text editor with vim mode enabled, the default keyboard shortcut "Shift + Enter" not does not work, the selected code is not sent to the console and run.
The following manual tests are done:
Enable vim mode, hit "Shift + Enter", fail
Enable vim mode, click "Run Selected Code" in run menu with mouse, succeed
Enable vim mode, change keyboard shortcut to "Ctrl + Enter", succeed
Disable vim mode, both keyboard shortcut and run menu succeed
Reproduce
Open a python file with text editor, enable vim mode
Create a console for this editor
Try running selected code by hitting "Shift + Enter"
Context
Operating System and version: Arch Linux
Browser and version: Chrome Version 130.0.6723.70 (Official Build) (64-bit)
JupyterLab version: 4.3.0
jupyterlab-vim version: 4.1.4
Jupyterlab labextension list shows
JupyterLab v4.3.0
/home/sk/.local/pipx/venvs/jupyterlab/share/jupyter/labextensions
jupyterlab_pygments v0.3.0 enabled OK (python, jupyterlab_pygments)
@axlair/jupyterlab_vim v4.1.4 enabled OK (python, jupyterlab_vim)
This keyboard issue may have occurred as early as Jupyterlab version 4.2.0, when I had just upgraded to 4.2.0. But I did not try disabling vim mode and changing to a different shortcut at that time. I simply rolled back to versions < 4.2.0 to work around. Until recently 4.3.0 released, I upgraded and found the issue still not fixed. I tried disabling vim mode and changing to a different to do further investigation.
Description
When trying to run selected code in a text editor with vim mode enabled, the default keyboard shortcut "Shift + Enter" not does not work, the selected code is not sent to the console and run.
The following manual tests are done:
Reproduce
Context
Jupyterlab labextension list
showsThis keyboard issue may have occurred as early as Jupyterlab version 4.2.0, when I had just upgraded to 4.2.0. But I did not try disabling vim mode and changing to a different shortcut at that time. I simply rolled back to versions < 4.2.0 to work around. Until recently 4.3.0 released, I upgraded and found the issue still not fixed. I tried disabling vim mode and changing to a different to do further investigation.
Same issue was raised in jupyterlab repo jupyterlab/jupyterlab#16939
The text was updated successfully, but these errors were encountered: