Looks like this was noticed in #152 but has no dedicated issue.  In #152 it was mentioned that this might be a sublime change, perhaps we could add some automated tests and bisect the offending sublime version.
