posit-dev / posit-dev/positron

Positron Notebooks - "don't save" appears to not work.

Open
#9,875 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: notebooks-jupyter area: notebooks-stability
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 11h
Merged PRs (30d)
206

Description

System details:

Positron and OS details:

Positron Version: 2025.11.0 build 39
Code - OSS Version: 1.103.0
Commit: f468a7958e3bf0eb0f76db4a5503ecf8f945e08a
Date: 2025-10-09T07:11:40.927Z
Electron: 37.2.3
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Darwin arm64 25.0.0

Session details:

N/A

Describe the issue:

If you modify a Positron notebook and close it and when it prompts to save you select "Don't Save" then reopen, your edits are still present.

Steps to reproduce the issue:

  1. Open a Positron notebook
  2. Make edits
  3. click to close
  4. select "Don't Save"
  5. reopen
  6. note that changes are present

I think that the file actually isn't saved. If you close and reopen Positron, you will see that the save didn't happen, but it appears that it did before you quit positron and reopen.

Expected or desired behavior:

When don't save is selected and the notebook is reopened, the changes made should not appear

Were there any error messages in the UI, Output panel, or Developer Tools console?

No

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

Reproduce the issue with a Positron notebook by editing it, choosing "Don't Save," closing it, and reopening it. Trace the notebook close and reopen handling to determine why discarded edits remain visible; done means reopening before restarting Positron shows the original content, with the existing reproduction steps covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
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.