Complete Emmet 2.0 support

[ramya-rao-a]

Contd. from #21943

Emmet Actions:

• Increment/Decrement by n
• Evaluate Math Expression
• Toggle Comment
• Multi cursor support for Wrap with abbreviation and Expand abbr commands Wrap with abbreviation and Expand abbr commands do not work with multiple cursors #27621

Port current Emmet customizations to the new model:

• Emmet: Expand Abbreviation command in languages that are not supported by emmet explicitly like php 1.13.0 | New Emmet expansion suggestions don't honor emmet.syntaxProfiles setting #28286
• Port customization of output profile
• Port customization of variables in emmet snippet. In new emmet, this will be via a new setting emmet.variables
• Port the use of emmet.extensionsPath for custom variables and profiles "emmet.extensionsPath" incompatible with "emmet.useNewEmmet": true #28465
• Port the use of emmet.exlcudeLanguages

Optimize Emmet expansions

• Use right language in case of embedded language. For eg: <style> block in html should use css Emmet css abbreviation not expanded in style block in html file #28039
• Use regex to filter out invalid abbreviations. Invalid emmet abbr returns weird expanded value in css files #27628 and Emmet resolves invalid format #27975
• Dont provide emmet suggestion inside the html tag or inside css selectors New Emmet completes html attribute as tag #28829
• Use VS Code specific stream reader for more efficient html and css parser
• Enable language extensions to call emmet completion provider Enable language extensions to call emmet completion provider #29114

Others:

• Add typings

Deferred Emmet Actions:

• Update Image Size (Pending resolution of Pull image-size and locate-file out of atom-plugin and into their own module emmetio/atom-plugin#21)
• Reflect CSS Value (No re-usable module from emmet yet. We should probably do this on our own)

[Fred-Vatin]

Just to be sure the follow will be considered.

Currently, users need to assign custom keybinding to Emmet commands to use it in a efficient workflow.

Question 1

I see among the available commands that Emmet has 2 flavors for some of them such as:

emmet.nextEditPoint
editor.emmet.action.nextEditPoint

Do they refer to new vs old emmet implementation? Witch one to use in future?

Question 2

If user set this custom keybinding

// Increment Number by 1
  {
      "key": "ctrl+up",
      "command": "editor.emmet.action.incrementNumberByOne",
      "when": "editorTextFocus && !editorReadonly"
  }

What would be the way to only enable this keybinding according to context (when emmet can effectively use this command)?

This would allow user to use the same keybinding for anything else or keep the default one working when the emmet context if FALSE (typically in this case: not in emmet supported language && caret not around numbers).

// Default VSC keybinding that could keep working even with the custom emmet set by user
{
  "key": "ctrl+up",
  "command": "scrollLineUp",
  "when": "editorTextFocus"
}

[ramya-rao-a]

@Fremea

To your first question:

• When emmet.useNewEmmet is set to false, editor.emmet.action.nextEditPoint uses old implementation and emmet.nextEditPoint uses the new one
• When emmet.useNewEmmet is set to true, editor.emmet.action.nextEditPoint calls emmet.nextEditPoint internally
• Eventually (some time when we deprecate the setting emmet.useNewEmmet and make the new implementation the default), you will have only editor.emmet.action.nextEditPoint which will use the new implementation

This is done so that users who have keybindings to the editor.emmet.action.... don't have to change their key bindings

To your second question:

The when clause can work on file types as well. So you can add resourceLangId == html and restrict few of the emmet commands based on file type. See https://code.visualstudio.com/docs/getstarted/keybindings#_when-clause-contexts

I don't think using cursor position is possible in the when clause.

Hope that helps

[Fred-Vatin]

@ramya-rao-a

Thanks for your answers.

The problem with editorLangId in when clause is that you must duplicate your keybinding as many times as there are languages to restrict.

It could be partially solved if when clause supported OR operator such as:

"when": "editorTextFocus && ( (editorLangId == html) || (editorLangId == css) || (editorLangId == js) || (editorLangId == xml) )"

But it wouldn't be as powerful and smart as a contextual Boolean state of command at caret position (instead of language used by file). It would allow using same keybinding for different commands in the same file depending on emmet context.

[nanaasumadu]

@ramya-rao-a

The new Emmet does not work in php document with embedded html. Can PHP be added to the supported language??

A test case.

1. Create standard html document.
2. Change the extension from html to php
3. Insert HTML element and child elements using emmet format.

[ramya-rao-a]

@nanaasumadu Have you tried adding the below setting?

"emmet.syntaxProfiles":{
"php": "html"
}