Skip to content
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

Feature request: Notebook emits Signal on run, announcing what was run #4740

Closed
mkery opened this issue Jun 18, 2018 · 0 comments · Fixed by #4744
Closed

Feature request: Notebook emits Signal on run, announcing what was run #4740

mkery opened this issue Jun 18, 2018 · 0 comments · Fixed by #4744

Comments

@mkery
Copy link

@mkery mkery commented Jun 18, 2018

Currently there is a signal available on a cell cell.model.stateChanged with the name executionCount that is emitted twice when a cell is run: 1st when the execution count is set to null before the cell is run, and 2nd when the execution count is set to a new number.

However, currently there is no way to directly detect:

  • when a Markdown cell is run (or any other cell type that does not have an execution count)
  • when "run all" is invoked, the full set of widgets that are run

A full list of widgets run is available when it is computed in runSelected of actions.ts. Requesting that a new signal type is emitted in Notebook like "widgetsRun" with the list of widgets run.

The primary use case I have is a JupyterLab extension that listens to run event fires on run, such as:

  • a logger/history based tool
  • a program analysis tool
  • collaboration (if Alice is working on a cell at the same as Bob, Alice could get a signal when Bob gets a new result, even if she doesn't want to see Bob's current editing since she's working on the same cell)
  • something that watches Markdown cells, like a table of contents extension, needs to know when to update
@afshin afshin self-assigned this Jun 18, 2018
@afshin afshin closed this in #4744 Jun 20, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants