Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python colorcoding broken? #37

Closed
objarni opened this issue Nov 7, 2014 · 4 comments
Closed

Python colorcoding broken? #37

objarni opened this issue Nov 7, 2014 · 4 comments

Comments

@objarni
Copy link

objarni commented Nov 7, 2014

I was under the impression the color coding was supposed to identify variables ('names' in Python lingua) and not whole rows? This just looks weird....
colorcoderpythonst3

OS: Ubuntu 14.04 64-bit
Software: Sublime Text 3
Install: via package control

@objarni
Copy link
Author

objarni commented Nov 7, 2014

I get the same problem in C++; keywords and method names are colored, but not local variables. Is this expected behaviour?

@objarni
Copy link
Author

objarni commented Nov 7, 2014

OK I found this thread on the Sublime Text forum, that gave me the solution: via command palette choose syntax highlighter. Is it not possible for Colorcoder to do this automatically, on detecting what language is used in the buffer?

@vprimachenko
Copy link
Owner

this is expected behaviour (or better, i expect the user to change the language manually or set them as default) as default languages don't provide the needed level of fidelity in terms of token distinction – hence i provide special colorcoded languages (as noted in readme).

Theoretically it is possible for colorcoder to automatically switch the definitions, but i restrained from implementing this as:

  • the user can simply set the colorcoded languages as default for filetype via language menuOpen all with current extension asColorcoder… (Colorcoded)
  • this functionality would interfere with other appropiate-syntax-select plugins like excellent ApplySyntax
  • because of bugs like Colorcoders tmLanguages break Go to Symbol feature #9 i prefer to leave the choice to the user

@objarni
Copy link
Author

objarni commented Nov 9, 2014

Thank you!

I will definitely go for the default language for extension as I already - after using this only for a day - feel in better control of my code - this package enhances "local readability" for a method a lot.

By reading through the whole doc page I see this is documented under the header "Supported languages". I would have expected this to be part of the header "Installation" as I expect plugins to start working once installed (after a ST reboot at least), or if anything like this is necessary to set them up, I expect it to be documented under "Installation".

Thanks for a great plugin!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants