MagicPython doesn't work with VS Code under Windows 10

[jakeargent]

• Editor name and version: Visual Studio Code 1.2.1
• Platform: Windows 10
• Color scheme: Default
• MagicPython version: 0.5.11
• A sreenshot:
  
• 5-10 lines of surrounding code:

I've had this issue for a while now, and it's slightly different in Windows 10 vs Linux Mint 17.3. In LM17.3 there's some coloring. For example def func(arg1, arg2): would have def as blue, func as yellow-ish, and the rest as white.

In any case, with Windows 10 the extension flat-out doesn't work as you can see in the screenshot.

[1st1]

I'm not sure I see the problem -- everything is seems to be properly highlighted in the screenshot, albeit it seems that the linter is complaining about code style. Do you mean that MagicPython does not highlight function and coroutine names with a yellow color as the built-in VSCode Python highlighter does?

[jakeargent]

I've taken this screenshot with these lines as a comparison with the screenshot at the MagicPython github page. In that picture showcase is colored green, docstring and regular string are colored differently, and the parameter of the @decorator and it's assigned value are also colored, and different from each other.

Should I not expect these? If not, what should I expect with MagicPython?

P.S: I have MagicPython installed in both W10 and LM17.3 for VS Code. It behaves slightly differently between these OS's and its behavior doesn't match (or come close) to that of the screenshot present in the github page.

This is the picture I'm talking about.

Linter's complaint is a red herring here.

[1st1]

Should I not expect these? If not, what should I expect with MagicPython?

Syntax highlighting is generally implemented with two components:

1. Language Schema. This is what MagicPython is. It parses Python language and tags each symbol with a special class or set of classes.
2. Color Schemas. They assign colors to classes that language schemas tag symbols with.

The screenshot you're referring to is MagicPython combined with Chromodynamics. The latter is only available for Atom and Sublime Text, but I think it shouldn't be hard to convert it to VSCode. You can either try doing that, or experiment with different color schemas in VSCode. Of the standard ones, Monokai works good enough.

[jakeargent]

That clears up some confusion and I'll close this issue.

How would I go about converting Chromodynamics to work with VS Code though? I've looked at alternatives and... they are better than default, but not that much.

Edit: Installed Node.js, then installed yeoman code, and created a theme file using chromodynamics tmTheme as template... easy as you said.

Thanks for the pointer!

[1st1]

Please open an issue for VSCode compat for the Chromodynamics project. I'll try to take a look.

[scotthuang1989]

I can't install it on atom on windows 10. maybe it is the same issue?