-
Notifications
You must be signed in to change notification settings - Fork 50
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
Emmet doesn't work in eex files. #11
Comments
Noticed this as well, will look into it once i find some time |
Just to clarify whats going on (at least how I understand it): The filetypes in which Emmet is enabled are hardcoded in the vscode source at the moment. That means the only way we could get emmet to work in This means we are blocked on the issue above with this. Good news is that it's on the milestone for august. Update: It's merged so if the next release goes out this is ready to work on. Update 2: It's ready to work on. |
I looked into this and tried to implement it like it is done in vscode-vash and described here but I couldn't yet get it to work. @fr1zle could you explain to me why there are two files for eex syntax (eex.json and html (eex).json)? I don't quite get the difference. @MRMInc sorry for bothering you with this extension but you seem to have it working with vscode-vash. Can you tell at a glance why it isn't already working for |
In your case you have incorrect format identifiers. See:
Now you can use the following format: "emmet.syntaxProfiles": {
"HTML (Eex)": "html"
} Emmet does not work by default because we have a rule: If the language ID is not equal to last value in |
I have added
to my config and reloaded, yet emmet still doesn't work on Eex files. My |
Can reproduce. Seems to be an issue with the new emmet (2.0): https://code.visualstudio.com/docs/editor/emmet |
@Pranz - try adding |
@ashleyconnor : This seems to work when a added to a user settings. Somehow this does not work if I add a contribution to the extension providing the setting... Any ideas? |
@ashleyconnor Thanks, works if I put it in my user config. |
@ashleyconnor thank you so much. |
Now its "HTML (EEx)" not "HTML (Eex)" |
If you're using elixir-ls plugin - it's now: "html-eex": "html" |
All before not working for me, and find that use "emmet.includeLanguages" with "html-eex": "html"
|
|
Unfortunately this applies outside of sigils too, but yes, you can
The key is the language type, and the value is an "emmet supported language", although what those values are is a bit ambiguous (see microsoft/vscode-docs#3935) |
For anyone looking support for the new
"emmet.includeLanguages": {
...
"phoenix-heex": "html",
...
} |
If you hit
tab
or fire the emmet expand abbr. command via the command it just makes a tab in eex files. I think it would be nice if it kept working like it does in HTML.The text was updated successfully, but these errors were encountered: