News for hackers. Stuff that matters.
Re:Sublime Text 3.0 by tombusby on Wednesday September 13, 2017 @05:29PM (#15242890)
Speaking of, the GitGutter plugin I use just broke on this update.

https://github.com/jisaacks/GitGutter

Doesn't even appear in the installable list now. Hopefully he'll get some of these hickups with package manager sorted.

Re:Sublime Text 3.0 by wbond on Wednesday September 13, 2017 @06:25PM (#15243305)
If it isn't in the installable list, you may have it installed already.

Package Control is open source and contributions are welcome! We finally get to rip out support for ST2 and Python 2.6 now also!

Re:Sublime Text 3.0 by tombusby on Thursday September 14, 2017 @07:59AM (#15247030)
Yeah that was a part of the problem.

https://github.com/jisaacks/GitGutter/issues/444

It was still installed... but broken.

Re:Sublime Text 3.0 by geoelectric on Wednesday September 13, 2017 @06:10PM (#15243199)
Weird, it was the first thing I installed after installing 3.0 as a new install. Wonder if it's an update issue in particular.
Re:Sublime Text 3.0 by tombusby on Thursday September 14, 2017 @07:58AM (#15247018)
It's an update issue, I'm talking to a fair few people who had the same issue on a GitHub issue. I have resolved it now.

This update appears to have broken a lot of plugins.

Re:Sublime Text 3.0 by geoelectric on Thursday September 14, 2017 @07:37PM (#15253395)
Sorry, bad wording on my part. By update issue I meant something where you had to have the version already installed prior to updating, vs. a fresh install (which worked for me).
Re:Sublime Text 3.0 by wbond on Thursday September 14, 2017 @08:28AM (#15247241)
I don't think ST3 broke anything. More likely Package Control 3.3.0, that was released three days ago, is the issue.
Re:Sublime Text 3.0 by karthik248 on Wednesday September 13, 2017 @11:18PM (#15244757)
Immediately after the update if wasn't working, but restarting sublime seems to have fixed it