-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Serialized workspace states are incompatible after disabling the package #90
Comments
When you disable CR from Atom's package manager it can restore the state of the workspace when you installed it, but due to an Atom limitation we can't fix the serialized state for closed / inactive workspaces. Launching atom with the We can fix the current / active / open workspace when the package is disabled, but the best I can think of for fixing closed / inactive workspaces with serialized CR elements in them would be to send a notification to the user when the package is disabled as a reminder to clear the window state. I think this might warrant a change to upstream Atom, something like a failsafe in case Atom can't find the deserializer for a no-longer-active package. |
I tried to disable code-ribbon (from Atom but the change is visible in config.cson).
This broke Atom completely. When I try to open it there is only a black window without any files, treeview or anything else and it does not load anything even if I wait for 2 minutes.
The text was updated successfully, but these errors were encountered: