Did you try the Emmet: Expand Abbreviation command or you are expecting the auto completion?

The former should work. The latter I disabled as it becomes too noisy when emmet suggestions pop up every where in the while instead of just the html/css parts of the file.

@ramya-rao-a I tried auto completion, if that's not supported maybe there should be a note in the setting description?

@ramya-rao-a it worked via command.

@ramya-rao-a I can't imagine actually doing this and finding it useful. There should be a note in the description though to make it clear how to use it for people like me who don't really use the command.

Using syntaxProfiles for mapping a language to one of the emmet supported ones was introduced back in September. See https://code.visualstudio.com/updates/v1_5#_settings-to-enabledisable-emmet-for-languages

syntaxProfiles was already being used for a whole different purpose. Which was to define the output profile as defnied here: https://docs.emmet.io/customization/syntax-profiles/

This was re-used in September to be used for enabling emmet in other languages.

Back in February, I fixed a few issues around this. But the real fix is to separate the output profile settings from the language mapping settings which I have been wanting to do for a while.

Here is my proposal:

In the new emmet model, we will use a new setting emmet.includeLanguages to enable emmet abbreviations in languages that are not supported by default.
emmet.syntaxProfiles will be used only for setting the output profile as defined https://docs.emmet.io/customization/syntax-profiles/ and not to map languages to emmet supported modes

Pros:

• Intuitive to new users
• No confusion to emmet users coming from other editors as syntaxProfiles means exactly what was documented in the emmet website https://docs.emmet.io/customization/syntax-profiles/
• Naming is self-explanatory and is a good opposite to emmet.excludeLanguages
• This will only come into affect when emmet.useNewEmmet is true

Cons

• Existing VS Code emmet users who have been using emmet.syntaxProfiles to map languages will have to make a change.
• There are a few docs and tweets out there that we need to update

cc @egamma @mrmlnc

I found it now emmet.syntaxProfiles & emmet.useNewEmmet: true can not coexist (
For example: I set vue to syntaxProfiles, and then set useNewEmmet: true, in the vue file emmet can not be used.

@ifzm Are you referring to the Emmet: Expand Abbreviation command or the emmet abbreviations showing up in the suggestion list? The former should work as long as you have the mapping "vue-html": "html". The suggestions will work once they are implemented by language specific extensions. You can follow #29114

Thanks for your answer ).
Yes，i think I may not be clear, the actual problem is this "emmet.syntaxProfiles" not working with "emmet.useNewEmmet" (emmet 2.0)

I like your proposal!

The new settings emmet.includeLanguages is a nice problem.

The new setting emmet.includeLanguages is a nice proposal.

I had a day to think about this and am going ahead with it.
The pros in #29678 (comment) outweigh the cons

emmet.includeLanguages will be used in the new emmet model to map languages unsupported by emmet to one of the languages that is supported by emmet.

emmet.sytnaxProfiles will continued to be used for the same purpose, but only in the old emmet model

yay!

The change will be available in the next Insiders (29th June, 2017)

nice 👍

@ramya-rao-a is this deployed yet?

In the Insiders, yes.
For the stable build, wait for the release of VS Code 1.14
In both cases ensure "emmet.useNewEmmet" is ser to true

VERSION: 1.14

My user settings contained the following:

    "emmet.useNewEmmet": true,
    "emmet.syntaxProfiles": {"handlebars": "html"},
    "emmet.includeLanguages": {"handlebars": "html"},

Emmet wasn't available in my handlebars files :(

Only fix was "emmet.showExpandedAbbreviation": "always"

@Elyx0 That is covered in #28545 Please follow that issue

If anyone else wound up here trying to get html snippets to work in *.blade.php files, the fix is to add them to blade.json instead of html.json from the User Snippets menu.