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

Package Control updates require a Sublime Restart #31

Open
Oblongmana opened this issue Jan 8, 2016 · 2 comments
Open

Package Control updates require a Sublime Restart #31

Oblongmana opened this issue Jan 8, 2016 · 2 comments
Labels
Milestone

Comments

@Oblongmana
Copy link
Owner

Updates pushed out by package control appear to require a sublime restart.

This is possibly a consequence of the non-flat folder structure introduced a few releases ago, where the plugin was broken into multiple files, some of which are in a folder. These do not appear to get reloaded by Sublime when these files change (unlike files in the plugin root).

If possible, it would be nice to not require a Sublime restart when Package Control pushes an update

@Oblongmana Oblongmana added the bug label Jan 8, 2016
@Oblongmana Oblongmana added this to the 2.2.0 milestone Jan 8, 2016
@coldeagle
Copy link

I'm not sure if this is related or not, but I had a problem with a Windows installation. For some reason the installer is creating a folder called "Salesforce Reference"; however, when I try to look up the default it's looking for "SublimeSalesforceReference". I even tried to re-name the folder; however, on restart it was back to the old name.

@Oblongmana
Copy link
Owner Author

@coldeagle Sounds like an odd one - not sure I fully understand the issue? There should be a folder called Salesforce Reference in your Sublime Packages folder - can you elaborate on this bit a little?

when I try to look up the default it's looking for "SublimeSalesforceReference"

@Oblongmana Oblongmana modified the milestones: 2.2.0, 2.3.0 Jun 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants