Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Som Notebook Keyboard Shortcuts does not work. #4420

Closed
zhouwangyang opened this issue Jan 18, 2021 · 4 comments
Closed

Som Notebook Keyboard Shortcuts does not work. #4420

zhouwangyang opened this issue Jan 18, 2021 · 4 comments
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@zhouwangyang
Copy link

Environment data

Version: 1.53.0-insider (user setup)
Commit: eaa959d34b863dec932077d94daece22504a396b
Date: 2021-01-18T05:13:25.733Z
Electron: 11.2.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.17134
anaconda: python 3.8.5(64 bit)
Build of python-insider: 2020.12.414227025
Build of Jupyter-insider: 2021.1.481581316-rc

Expected behaviour

these Notebook Keyboard Shortcuts should work well.

Actual behaviour

Keyboard Shortcuts does not work, among them, after hit ctrl+enter , a cell runs and a new cell is added below.

Steps to reproduce:

  1. Using the notebook generated from the manualTestFile.py, do the following:
  2. Hit o on a code cell with output and verify that outputs disappear
  3. Hit z and verify a deleted cell reappears
  4. Hit ctrl+enter and verify a cell runs and selection does not change
@zhouwangyang zhouwangyang added the bug Issue identified by VS Code Team member as probable bug label Jan 18, 2021
@joyceerhl
Copy link
Contributor

@zhouwangyang, sorry for the trouble here. If you're looking to run a cell in-place, I believe ctrl+alt+enter on Windows is the shortcut you're looking for. Which other notebook shortcuts are not working for you?

@IanMatthewHuff
Copy link
Member

I believe that most of these would be covered by this issue, which we have still not resolved yet:
#4376

I think these are just not available in the new interface until that point.

@joyceerhl
Copy link
Contributor

Oh, missed that one @IanMatthewHuff. Thanks for the pointer. I think we can close this one as a dupe then?

@greazer
Copy link
Member

greazer commented Jan 21, 2021

This is a dupe of #4376

@greazer greazer closed this as completed Jan 21, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants