I followed the instructions in this blog post Multiple Fonts: Alternative to Operator Mono in VSCode, but did not see any changes made to VS Code. After digging a bit, I discovered that all the CSS class names had changed. They’re now e.g. .mtk13, .mtk16 { … }
.
- Ensure it’s a file URL e.g.
{ "vscode_custom_css.imports": [ "file:///Users/Brian/Desktop/vscode-style.css" ] }
- If you move the location of your file and update your user settings with the new location, you will need to disable and enable custom CSS cmd+shift+p.
- Also, anytime you change the style in your custom CSS file, you need to disable, then re-enable the extension.
I havent tried it yet, but I did spend several hours digging through the Dev Console to get the glow to work (a la synthwave84 - an amazing theme. I have a very heavily modified theme that will be appearing on the extension store shortly. I took his theme and then cranked it wayyy up, redoing every definition for color, etc. Any, not the point.
BUT- you notice in the css - that the themes upon inspection-
F1 - Open Dev Console - then [[Ctrl]]+[[c]] to turn on the selector, and then hover over the token-
you are modifying the token values- (which btw I am suspicious that they may vary dynamically as theyre assigned based on need, though I heavily use one language so I cant tell yet. But- to the point-- you are modifying .mtkNN {
} to modify a value, but the parent class is perhaps easier.
![image](https://user-images.githubusercontent.com/15314341/63642075-ea58bc00-c6a8-11e9-95de-f00b73757154.png)
You can see the style is
So it would be easier to extend
mtkb
,mtki
andmtku
like this
blob:file:///d3ff5411-221b-48b8-8d60-49a15ca5ba54