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

Native Editor - implement dirty tracking files for ipynb #3061

Closed
rchiodo opened this issue Sep 16, 2019 · 1 comment
Closed

Native Editor - implement dirty tracking files for ipynb #3061

rchiodo opened this issue Sep 16, 2019 · 1 comment
Assignees

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Sep 16, 2019

In issue microsoft/vscode-python#7258 there are multiple options discussed. The ideal situation is option 4:

Option 4: Implement behavior similar to VSCode's auto-recover functionality that stores a dirty copy of what was edited and when VSCode is launched again, it displays that file as dirty. This is considerably more expensive than the other options here.

This issue is to make sure option 4 is implemented at some point.

@rchiodo rchiodo self-assigned this Sep 20, 2019
@IanMatthewHuff IanMatthewHuff self-assigned this Sep 23, 2019
@IanMatthewHuff
Copy link
Member

I felt like I got it in a state once where it was asking me to save a file on close that I hadn't made dirty, but I was unable to get a repro on that with a bunch of trying. So validated.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 1, 2019
@microsoft microsoft unlocked this conversation Nov 14, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants