Closed IanCaunce closed 9 years ago
Thanks for reporting. I'll use this occasion to switch to a tag-based versioning system (as endorsed by PC 3.0) and get rid off the old messages. Pull request to the Package Control channel is pending.
Please let me know if the latest update works for you. In worst case you'll have to re-install the package, but in any case let me know how it went. Thanks!
Hi, Unfortunately I already solved the issue before the fixed package was released by uninstalling the old one and installing the new one with the bug. I think the missing file was only an issue if upgrading. However, I can say that upgrading from the buggy package to the latest version went smoothly without any issues.
Thanks, for sorting it promptly and thanks for the awesome sublime package.
Cool, thanks
After the latest update package control fails to update this package. This in turn stops any other package from updating and which causes them to remain disabled. (I believe they are disabled as part of the update process.) Restarting sublime has no effect.
It fails saying that the file .messages/four_new_fonts.txt is missing which is printed to the console.
The only way I could solve the issue is by removing your package and reinstalling it. I then had to enable all the other packages which where disabled as part of the update process.
Unfortunately, I didn't save the full debug log from the console. My apologies
Edit: After further inspection, inside messages.json a line reads: "2014.12.20.00.00.00": ".messages/four_new_fonts.txt"
Inside the .messages folder the file is called "four_new_icons.txt"