material2-snippets
material2-snippets copied to clipboard
Can't get @fx to work in VSCode
All the other snippets work fine but @fx doesn't work. I've tried something very basic such as
<div @fx>
</div>
but I get no options even which I hit control + space
Very strange. For whatever reason it is now working.
same here, but no luck
@rexhxiao I am using the latest version of insiders build. I am not sure how to reproduce the issue.
Please note that the extension will get activated only if the file opened has one of the following languages enabled.
blade ejs html handlebars latte php plaintext razor tpl typescript typescriptreact twig
Can you try uninstalling the extension, closing the editor & reinstalling the extension.
@thekalinga Follow your suggestions, but still same problem even just open a new window and a new html file. Thank you all the same.
@rexhxiao Can you try opening an existing html file

Hi,
Thanks for the gif. I tried in my regular code build (1.13.1). The snippets that that starts with @fx is not working for some reason (not yet sure why that's the case).
However, its working in insiders build (I use this in my dev env).
Can you please confirm if you its working for you in insiders build. https://code.visualstudio.com/insiders
Also,
Can you check in your current non-insiders build whether pressing ctrl+space immediately after @ shows @fx.. suggestions instead of pressing ctrl+space after typing @fx
In my env (non insiders), @ and ctrl+space shows suggestions of @fx..
I think i found reason why can't shows suggestions, because My default input language is set to Chinese Traditional.
So if i type ctrl + space that nothing happened (only windows IME switch), then just remove all and only use input language for English, everything is fine!
How can i fix the IME problem?
ps. my env is win10 eng.
Also did u try this in insiders build?
Also is this happening just with extension/with with just snippets that start with @/with other snippet extensions aswell?
Again, I don't use windows. :( Not sure how this issue can be remedied.
If this is happening with other extensions too, then the issue must be in vscode. But if this is happening just with this extension & other extensions are working fine, must be something wrong within this extension
Yes, ctrl + space perfect work on the insiders build.
You are right, same IME problem with other extensions. But still some bug without IME, please see gif.
