Vscode: emmet.extensions not working

[kangTaehee]

Issue Type: Bug

The "emmet.extensionsPath" related settings do not work after the update.
Before the update, I was using it well.

It's the same thing with the reinstallation and the samples.

VS Code version: Code 1.48.0 (db40434f562994116e5b21c24015a2e40b2504e6, 2020-08-13T07:50:42.600Z)
OS version: Windows_NT x64 10.0.18363

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.90GB (9.21GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

Extensions: none

[shurinskiy]

Yes, that is right. After the update, custom snippets stopped picking up. It became inconvenient to work. This is a very useful tool.

[TD540]

Not working here also:
VS Code version: 1.48.2
OS version: macOS Catalina

[poltavchenko]

When do you plan to fix this bug?

[shurinskiy]

There have been four updates since the error appeared

[poltavchenko]

There have been four updates since the error appeared

ok, in the latest build the problem is solved?

[shurinskiy]

There have been four updates since the error appeared

ok, in the latest build the problem is solved?

No! This is the problem. Already four updates in a row, such a necessary tool is ignored :(

[rzhao271]

Reopening because it auto-closed.
@TD540 can you confirm whether the fix works tomorrow in the next insiders build for macOS? Thanks in advance

[rzhao271]

Confirmed it works on latest Windows insiders. Will re-close and add this issue to current milestone.

[rzhao271]

/closedwith 2dbd0ae6a49e64c32611c4206c0917f7144d4051

[vscode-triage-bot]

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, then add back the unreleased label.

[rzhao271]

\closedWith 2dbd0ae

[TD540]

Thank you to whoever fixed this!

[rzhao271]

For verifiers:

1. Write an Emmet snippets file or use the example as per https://code.visualstudio.com/docs/editor/emmet
2. Change the emmet.extensionsPath setting to point to that file
3. Create a new HTML or CSS file and type one of the snippets. Ensure that the snippet is suggested in the Intellisense.