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

Undo stack lost at random times. #3443

Closed
tacho87 opened this issue Feb 25, 2016 · 12 comments
Closed

Undo stack lost at random times. #3443

tacho87 opened this issue Feb 25, 2016 · 12 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@tacho87
Copy link

tacho87 commented Feb 25, 2016

After 0.10.9 vscode does not preserve the undo/redo stack. Sometimes it preserves for 5 to 10 items. It was not behaving like this before upgrading.

@joaomoreno
Copy link
Member

@tacho87 Are you using OS X? Seems to be a duplicate of #3071. Related to #2829.

@joaomoreno joaomoreno added the info-needed Issue requires more information from poster label Feb 25, 2016
@alexdima
Copy link
Member

@tacho87 Can you please share some reproducible steps?

@tacho87
Copy link
Author

tacho87 commented Mar 3, 2016

Yes I am using OSX, vscode Version 0.10.9 (0.10.9).
I tried to reproduce it. It seems to happen when I change from vscode to the browser and go back on JSX files mostly. Unfortunately , I do not have any steps or scenarios to reproduce it.

It just feels like it is refreshing the redo/undo stack when something happens internally when using JSX files.

@alexdima
Copy link
Member

alexdima commented Mar 3, 2016

@tacho87 Is it possible that the files are changed on disk outside of VSCode? When a file changes on disk, we reload the file and drop the undo stack.

@tacho87
Copy link
Author

tacho87 commented Mar 3, 2016

I usually work on a share drive for backup purposes with git on it. Could that be the issue? I also experienced it today on a plain html/js file on my desktop. Seems to happen specially when I debug the js on chrome.

@alexdima
Copy link
Member

@tacho87 We drop the undo stack when the file is edited on disk outside of VSCode. If a file is merely touched (but has the same content), we don't drop the undo stack. Are you editing the files through the Chrome debugger?

@joaomoreno
Copy link
Member

@alexandrudima This could be a duplicate of #2908, if that question is answered positively.

@alexdima
Copy link
Member

alexdima commented Jul 7, 2016

Most likely it is #2908

@alexdima alexdima closed this as completed Jul 7, 2016
@warmhug
Copy link

warmhug commented Jul 29, 2016

On Mac, vs code's version of 1.3.1 also reproduce it

@bpasero
Copy link
Member

bpasero commented Aug 26, 2016

This is #10932

@StefanPatatu
Copy link

I can confirm the bug still exists as of v1.4.0. The bug mostly manifests after I save a file (work on file, CTRL+S, webpack rebuilds, check browser, see everything is broken, realize I have a typo or something, ALT+TAB, then CTRL+Z no longer works). It also manifests randomly sometimes, but especially after CTRL+S-ing.

@bpasero
Copy link
Member

bpasero commented Sep 13, 2016

@StefanPatatu what about Code 1.5 where we landed a fix?

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

6 participants