-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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.extensionsPath" incompatible with "emmet.useNewEmmet": true #28465
Labels
emmet
Emmet related issues
feature-request
Request for new features or functionality
verification-needed
Verification of issue is requested
verified
Verification succeeded
Milestone
Comments
Fred-Vatin
changed the title
Emmet: "emmet.extensionsPath" incompatible with "emmet.useNewEmmet": true
"emmet.extensionsPath" incompatible with "emmet.useNewEmmet": true
Jun 11, 2017
Yes, in the new emmet model, its not very straight forward to re-use the previous custom snippets I have included the investigation for this in #27697 Thanks for reporting! |
ramya-rao-a
added
feature-request
Request for new features or functionality
verification-needed
Verification of issue is requested
labels
Jun 26, 2017
Note to verifier:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
emmet
Emmet related issues
feature-request
Request for new features or functionality
verification-needed
Verification of issue is requested
verified
Verification succeeded
The new Emmet feature is awesome. Unfortunately, it will ignore the user setting "emmet.extensionsPath".
Steps to reproduce
Result
Custom emmet snippets are ignored. Lang applied is "en". Same goes for any emmet custom snippets in
"emmet.extensionsPath": "path to\\Emmet Settings"
: html, css, etc.It will work as intended if
"emmet.useNewEmmet": false
I hope this incompatibility issue with custom emmet settings will be solve.
The text was updated successfully, but these errors were encountered: