Interactive window theming is broken for the material theme
See original GitHub issueEnvironment data
- VS Code version: 1.34.0
- Extension version (available under the Extensions sidebar): 2019.5.17059
- OS and version: Ubuntu 18.04 LTS
- Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.3, Anaconda
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
- Relevant/affected Python packages and their versions: none
Expected behaviour
Correct theming of the Python interactive windows as in the version before. I am using material theme.
Actual behaviour
% 50 of the interactive window are occupied by the following, formated correctly like a markdown section:
Error: Illegal value for token color: at
in MonacoEditor
in div
in Code
in div
in div
in div
in div
in div
in Cell
in ErrorBoundary
in div
in div
in div
in MainPanel
Steps to reproduce:
- Use Material Theme extension, with material theme chosen
- Run cell in Python file
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
Starting Jedi Python language engine.
##########Linting Output - pylint##########
--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)
----------Generating Tags----------
ctags --options=/home/lukss/.vscode/extensions/ms-python.python-2019.5.17059/resources/ctagOptions --languages=Python --exclude=**/site-packages/** -o /home/lukss/Documents/DSP/stabilimetryAnalysis/.vscode/tags .
##########Linting Output - pylint##########
--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)
Output from Console
under the Developer Tools
panel (toggle Developer Tools on under Help
; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging
)
Info Python Extension: 2019-05-29 12:44:23: Wait for sys info for 09632ef2-c696-4cc9-85ea-267e4300bdd2 0
workbench.main.js:4167 [Embedded Page] Uncaught Error: Illegal value for token color:
Error: Illegal value for token color:
at ColorMap.getId (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:10100:19)
at resolveParsedTokenThemeRules (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:10083:58)
at Function.TokenTheme.createFromParsedTokenTheme (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:10128:16)
at Function.TokenTheme.createFromRawTokenTheme (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:10125:21)
at StandaloneTheme.get [as tokenTheme] (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:10570:47)
at TokenizationSupport2Adapter._toBinaryTokens (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:14348:65)
at TokenizationSupport2Adapter.tokenize2 (webpack:///./node_modules/monaco-editor/esm/vs/editor/editor.api.js_+_56_modules?:14380:27)
at ModelLinesTokens._updateTokensUntilLine (webpack:///./node_modules/monaco-editor/esm/vs/editor/common/model/textModel.js_+_10_modules?:4118:46)
at ModelLinesTokens._tokenizeOneLine (webpack:///./node_modules/monaco-editor/esm/vs/editor/common/model/textModel.js_+_10_modules?:4084:14)
at TextModel._revalidateTokensNow (webpack:///./node_modules/monaco-editor/esm/vs/editor/common/model/textModel.js_+_10_modules?:5758:52)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Angular Material styles not being applied correctly
In my case, I created an empty workspace, added a library, and then added an app project. I went back and ran ng...
Read more >Implementing your theme - Material Design
The following techniques can be used to customize and apply your theme color, typography, and shape. Iconography is provided with five unique sets...
Read more >Context menu in Windows 11 Insider bug for custom themes
In Windows 11 Insider when I open the context menu with active custom themes, I get this result: Anyone know how to fix...
Read more >Material Theme Changelog - KendoReact - Telerik
Now, we have have to base components: input and picker, that hold the bulk of styling needed. In addition, styles are split in...
Read more >Issues - GitHub
I got 6 themes, all working except the warning. ... Could not find Angular Material core theme, although all core @include mat-core(); is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The new update added intellisense support into the interactive window. That change required a change to the underlying editor we use. The old editor didn’t even read themes. The new one is the same one VS code uses and it can read theme values.
The theme values on the Material Theme are missing some foreground values (although this is likely on purpose)
This fix is in our insider’s build. To install our insider’s you don’t need vscode-insiders, but rather the insider’s vsix for our extension. It can be found here
You install this from the extension tab by uninstalling the python extension, clicking the ‘…’ in the upper right, and picking install from vsix.