Cell disabling not enough on windows :(

[laggvar]

I know the issue of cell disabling has been mentioned before was addressed in #985. The last comment in the related issue #298 suggests a better implementation, but was left unaddressed. Thus, the current solution requires the user to manually disable a cell every time after running it.

As a human being, I often forget to re-disable the cell, which means my computer gets stuck on long computations whenever I change something else. As I'm also forced to work on windows, I cannot interrupt a cell once it is running #452. This gives me the option of either waiting 10 minutes for the computation, or restarting the notebook and waiting for 5 minutes of loading + pre-computations.

If I cannot cancel a computation, it would be extremely helpful if I could put it into a mode where it at least can never run without my explicit permission. Essentially reactive by default, Jupyter-style as an opt-in (but without the hidden state 🙂).

A solution to #452 would of course also be ideal, but until then something better than the current cell disabling would be a significant improvement. It could also enable loading notebooks without automatically running the most expensive parts, improving on issues like #2242.

[fonsp]

#452 is close to being solved! Subscribe to that issue, more progress is coming soon.

For addition suggestions, could you use the feedback box instead? We appreciate the feedback!