search

SublimeLinter / SublimeLinter-rubocop

SublimeLinter 3 plugin for Ruby, using rubocop.
MIT License
159 stars 40 forks source link

Rubocop highlighting remains in buffer even after Sublime Text is restarted #4

Closed cimbriano closed 10 years ago

cimbriano commented 10 years ago

This issue was first described in a StackOverflow question since I was not sure at the time what was causing it.

http://stackoverflow.com/questions/21639983/unexpected-highlighting-in-sublime-text-3

Since then, I think I've narrowed down the issue.

OS: OSX 10.9.1 Build 13B42 Sublime Text : Stable Channel, Build 3059 Rubocop Package: v2014.02.01.19.05.03

After disabling Rubocop, I did not close the file, instead just used Cmd + Q to quit. Then when relaunching Sublime, the previously opened file was reopened/still open. This screenshot is after a restart and shows the Rubocop line highlighting and the results of Sublime's "Package Control: Enable Packages" (showing the currently disabled packages).

screen shot 2014-02-08 at 10 50 54 am

It appears that closing the file and restarting Sublime prevents seeing highlighting after the package is disabled.

cimbriano commented 10 years ago

Sorry. I think I wrote this on the wrong project.