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

!!! WARNING: ABANDONED PROJECT BREAKS SUBLIME TEXT 3 THEMES ON UNINSTALL !!! #479

Open
dustinbolton opened this issue May 29, 2020 · 2 comments

Comments

@dustinbolton
Copy link

dustinbolton commented May 29, 2020

WARNING: DO NOT USE THIS PLUGIN!

This is a warning to others. Not only does this plugin have many bugs in Sublime Text 3, including causing freezes, but it also will break your themes upon uninstalling (when you discover it's fairly broken as a plugin) as it moves theme files and makes modifications to files outside of the plugin itself. The author blames package control but either way, using this plugin is a risk until this is fixed.

There are multiple related issues about themes breaking on uninstall and problems with Sublime Text 3:
#341
#453
#474
#456
#476
#469

@judah-caruso
Copy link

Not sure how useful this is, but the plugin also modifies any .sublime-workspace file within your project. Deleting this file fixes artifacts left after uninstalling. If you're looking for a less-nuclear solution, a few bits of plugin data live within the groups array inside that file.

...
"groups":
[
    ...
    "settings":
    {
        "buffer_size": 94245,
        "regions":
        {
            "col_00000001":
            {
                "flags": 16,
                "regions": ...,
                "scope": "col_00000001"
            },
            "col_00000001_icon":
            {
                "flags": 16,
                "icon": "Packages/User/Color Highlight.cache/col_00000001_square.png",
                "regions": ...,
                "scope": "col_gutter"
            },
            ...
        }
    }
]

Deleting regions may or may not fix the issue (I haven't tested it), but it might get you out of the situation I was in without having to delete your entire workspace file.

@ngocphamm
Copy link

I solve the issue of this plugin after it being removed with this #453 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants