Ctrl+Enter should put cell into command mode after executing #6231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #6198
Following up on cb5ae1c I didn't notice that
ctrl+enter
for code cells doesn't behave the way users expect as well. Since I was working on resolving open keybindings issues I figured I'd go back and clean this particular problem up (should have been covered in #4438).The VS Code-contributed
ctrl+enter
keybinding fornotebook.cell.execute
will run the current cell but leave the cell in edit mode. This PR adds our own command which also takes the cell out of edit mode after running it, in order to match classic Jupyter behavior.