jupyter / jupyter/notebook

[Request] Keyboard shortcut parity with notebook classic

Open
#6,596 6 comments 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
Jupyter Notebook
Stars
13.3k
Forks
5.8k
Avg merge
6d 11h
Merged PRs (30d)
7

Description

Opening an issue to check the keyboard shortcut parity with the classic notebook.

This was originally posted by @lemontheme in https://github.com/jupyter/notebook/discussions/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.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the keyboard shortcuts described for Notebook classic with those in Notebook 7 and JupyterLab. The issue does not name files, tests, or an entry point; work would need an agreed shortcut scope and a way to verify parity before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.