Ryan Boehning

I'm experiencing the same issue. Tests in the `main` package are falsely reported as unused.

This issue has been fixed in [`golangci-lint`](https://github.com/golangci/golangci-lint/issues/116). I recommend using the [forked-and-fixed `deadcode`](https://github.com/golangci/golangci-lint/commit/001f788e3f804f5d1d857768b304b313b624ce52#diff-14ea331645fe6b7e35aaa77bb50ed34d) in that tool. ```sh golangci-lint run --disable-all --enable deadcode ```

This is a serious bug. Thanks for the PR @Dieterbe! I hope this will be reviewed soon.

@remyoudompheng You can close this PR now.

I just released [v2.1.29](https://github.com/ryboe/CSS3/releases/tag/v2.1.29), which will reenable inline styling. I had initially disabled it because of #107, but the issue appears to have gone away. If you see an error...

Thanks for reporting, @ashucg! Can you confirm that you're running the latest Sublime Text 3 build 3211? My working theory has been that something changed in a very recent build...

Ok, thanks for the quick reply, @ashucg. I've disabled inline highlighting again in [v2.1.30](https://github.com/ryboe/CSS3/releases/tag/v2.1.30), which should be released to Package Control in a hour or so.

I can confirm that hex values don't show up in auto-complete suggestions and agree that this would be a nice feature. I tinkered for an hour and wasn't able to...

Sorry, I haven't had time to work on this yet. I'm gonna work on it this weekend, though. It's definitely on my TODO list.

UPDATE: While I was working on improving the symbol indexing, I discovered that the new dev builds of Sublime Text 3 introduce an entirely new system for syntax highlighting. It's...