-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[Request] Keyboard shortcut parity with notebook classic #6596
Comments
This article might also be relevant: https://www.dataschool.io/jupyter-notebook-keyboard-shortcuts/ |
cc @Carreau since you opened a couple of recent issues about keyboard shortcuts |
That's a complicated story with likely some things that I would prefer to talk only face to face. You will be at JupyterCon right ? We can try to discuss this. |
Ah just to make it clear it was not me posting this message but @lemontheme. The discussion from #6591 was converted into an issue. I have updated the top comment to disambiguate this. |
Ah sorry, regardless. If someone wish to have some context, it's better to talk in person. |
adding some keyboard parity issues from lab |
Opening an issue to check the keyboard shortcut parity with the classic notebook.
This was originally posted by @lemontheme in #6591.
Posting the original message below:
Originally posted by lemontheme October 18, 2022
Excited to learn that future versions of notebook will be based off the same core as JupyterLab. I'm creating this post as a user who has tried to embrace JupyterLab but, despite all its great extra features, has always returned to notebook classic.
The reason: JupyterLab's keyboard shortcuts different enough that they frustrate many years of muscle memory built up in notebook classic. Sure, I can configure them to what I'm used to, but that means additional work each time I want to set up a (sometimes one-off) Jupyter environment somewhere.
Having just tried the Notebook 7 alpha, I can already tell the shortcuts are more like those in JupyterLab. I'm curious, does anyone know why JupyterLab didn't just keep the same shortcuts as before? It's always striked me as such a weird UX decision.
As for the question in my title, I'd like to float the idea of reversing that move in Notebook 7. Sooner or later, notebook classic users will be upgrading to notebook 7 without realizing the important changes beneath the surface. Doubtless many of them will be less than excited to learn they need to learn new shortcuts to get their work done faster.
Or is it just me?
Adding to the
7.0
milestone so it can be considered before the Notebook 7 final release.The text was updated successfully, but these errors were encountered: