jupyter / jupyter/notebook

Cell > All Output > Clear needs a popup warning

Open
#3,791 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
13.3k
Forks
5.8k
Avg merge
6d 11h
Merged PRs (30d)
7

Description

It's very helpful that the notebook includes a popup warning if you restart the kernel, informing you that all variables will be lost if you proceed. Since clearing all cell outputs may amount to pretty much the same thing depending on the nature of your code, this option (Cell > All Output > Clear) should have a similar popup warning.

In fact, there is actually *more* need for a popup warning for Clear Output because the menu structure makes it easy to do accidentally (not true for kernel restarts). In the Cell dropdown menu, if you move your mouse diagonally from the "Current Output" to the "Clear" option in the ensuing submenu, you may inadvertently mouseover and trigger the "All Output" submenu instead. This menu is precisely identical to the "Current Output" submenu, so it's easy not to notice. Then clicking the same "Clear" option suddenly and irrevocably clears your entire notebook.

I blame no one but myself for the seven hours of runtime I lost to said click -- but upon reflection it seems really, really easy to do this. I'm sure I'm not the first. Given how simple it would be to throw in a popup warning for this, I think it would be a helpful and sensible addition.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the Cell > All Output > Clear menu action and compare it with the existing kernel-restart warning described in the issue. Done means attempting to clear all cell outputs shows a confirmation popup before the irreversible action, including the risk of losing useful runtime results.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.