You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
@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"
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
The text was updated successfully, but these errors were encountered: