-
Notifications
You must be signed in to change notification settings - Fork 54
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
Not compatible with VS code version 1.10.2 #9
Comments
@JamDeezy Simply, click the "don't show again" on the "Your install is corrupted" message. |
@JamDeezy , the CSS is not working because those classes do not exist anymore. This is working for me (tried in javascript file only):
|
@made-aryadinata the Is there any documentation on how they changed these classes? I'd like to target specific keyword for this font. |
@JamDeezy use inspect element in Help > Toggle Developer Tools to see the class. |
@made-aryadinata thank you! |
The classes change and they don't scope correctly. For example, if "const" and "=>" have the same class... Changing themes and reloading VSCode also changed th.mkt12 to .mkt7 I don't think those mkt classes are a reliable identifier to use ligatures on specific keywords... Waiting for a solution... |
VSCode
|
@jkchuynh829 Thanks! works like a charm ! |
Is there some docs somewhere detailing information like this? |
The arrow function in vscode has the class mtk11, so the css should go like this:
|
Another route (which I had to take) was to add a textMateRule in my user settings:
|
Thanks @isabelacmor your solution was the trick I need it to add specificity to the classes, just in case works for someone else, I was looking to add Fira Code ligatures only to comparison operators and arrow functions, so:
Thanks to the underline style I can then match the vsc class name for underline (mtku) with the ones I want (eg. mtk13 - it may be different for you and it may be change every time you restart vsc)
:) |
This extension is not compatible with VS code version 1.10.2. It may be the same issue as PR #8, as the only time I can get this to work is to install 1.8.
Sample CSS that would've worked in 1.8.
The text was updated successfully, but these errors were encountered: