@rebornix you will get this for free once Notebooks register as working copy via IWorkingCopyService. I am actually surprised how notebooks are not registering already, how do you deal with e.g. hot-exit so far?

@bpasero we didn't do hot exit yet. We will hook it up in April, thanks for the pointer.

@rebornix actually disregard my suggestion to register a working copy, as it seems to me a notebook is always backed by a single text file, is that true?

If so, then you should just resolve the text model (e.g. via text model resolver service and the file URI) and work on that. This model will register itself automatically as working copy and will:

• auto save (if enabled)
• backup (on shutdown)

... it seems to me a notebook is always backed by a single text file, is that true?

We don't know that yet. As of today that's up to extensions to decide

@jrieken then it seems you will have to do what custom editors are doing depending on the implementation:

• backed by text document: custom editor does NOT register a working copy and use the existing model services
• not backed by text document: custom editor registers a working copy

The working copy service does not allow to register multiple working copies with the same exact resource because e.g. backups are associated with exactly one resource that needs to be unique.

IMHO the notebook is close to Custom Editor. The GitHub issues notebook can be text document based but we are not sure yet if it's valid for Jupyter notebook and other potential notebook use cases. We can discuss this in April's API meeting.

Test verify this issue, install the GH issues notebook extension: https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-github-issue-notebooks