Open
Description
openedon Oct 14, 2022
Applies To
- Notebooks (.ipynb files)
- Interactive Window and/or Cell Scripts (.py files with #%% markers)
What happened?
I use VIM mode and the Jupyter Interactive Window, but there are some conflicts in the text area of the interactive window:
-
The
<UP>
arrow does not work to get the previous cells content.- Neither does
k
when in VIM normal mode, as would also be expected.
- Neither does
-
The
<ESC>
key, used to go in VIM normal mode, clears the input area.- This is the same behavior than without VIM, although even there I would prefer that it does not clears the input area
- It is annoying to lost my input by inadvertently pressing
<ESC>
, which occurs often when using VIM. - The VIM modes are available in that input area:
<Ctrl-C>
(or other custom mapping) still works to go in VIM normal mode.
VS Code Version
Version: 1.72.1 Commit: 129500ee4c8ab7263461ffe327268ba56b9f210d Date: 2022-10-10T17:23:00.760Z Electron: 19.0.17 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Linux x64 5.14.0-1052-oem Sandboxed: No
Jupyter Extension Version
v2022.9.1202862440
Jupyter logs
No response
Coding Language and Runtime Version
Python v3.10.6
Language Extension Version (if applicable)
Python v2022.16.1
Anaconda Version (if applicable)
conda 22.9.0
Running Jupyter locally or remotely?
Local
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment