-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Comments
@tacho87 Can you please share some reproducible steps? |
Yes I am using OSX, vscode Version 0.10.9 (0.10.9). It just feels like it is refreshing the redo/undo stack when something happens internally when using JSX files. |
@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. |
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. |
@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? |
@alexandrudima This could be a duplicate of #2908, if that question is answered positively. |
Most likely it is #2908 |
On Mac, vs code's version of 1.3.1 also reproduce it |
This is #10932 |
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. |
@StefanPatatu what about Code 1.5 where we landed a fix? |
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.
The text was updated successfully, but these errors were encountered: