Skip to content
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 expansion seems to be interfering with this extension #30

Open
macintacos opened this issue Mar 7, 2017 · 5 comments
Open

Emmet expansion seems to be interfering with this extension #30

macintacos opened this issue Mar 7, 2017 · 5 comments

Comments

@macintacos
Copy link

Below you can see a .gif of the issue. When trying to tab-expand in an HTML file using Emmet, the expected expansion does not work with HTML Snippets enabled, but functions fine when HTML Snippets is disabled.

2017-03-07-emmet-expansion-not-working 1

I went through all of my extensions one-by-one to find this issue, so I'm pretty confident that it is this extension that is causing this. I can't reliably use this extension until this is fixed.

@abusaidm
Copy link
Owner

Hello @macintacos , yes there seems a conflict in the extensions, this is not a bug, this is a behaviour in the VSCode snippets/extensions engine. if you have an extension that is conflicting with other you would have to choose one or the other, I will try raise this with the VSCode developers but I don't see this behaviour as an issue in most cases.

Thank you

@macintacos
Copy link
Author

@abusaidm That's unfortunate, as most of the extensions seem to work fine together and I really like HTML Snippets...I'll do some more investigation and check to which is conflicting and see if I can get rid of the other extension instead.

@smoses2
Copy link

smoses2 commented May 10, 2017

I also really appreciate the Html snippets, but had to uninstall as it is breaking emmet functionality. Single item emmet/zen-html works fine (or maybe this is your autocompletion and not emmet), but those with sibling relationships or multi-level are breaking:
p+p
becomes p+

is there a way for your code to ignore lines that include +, unmatched >, ^, *
This would allow for emmet completion on these lines instead.

@abusaidm
Copy link
Owner

hello @smoses2 I know how annoying this can be when extensions conflict with each other, I am relying on the VSCode extension engine to handle all the work thats why I cant do much to resolve this, I would have to re-write the extension to work using my own engine just to achieve a custom behaviour

@smoses2
Copy link

smoses2 commented May 11, 2017

Thanks @abusaidm and again thanks for html snippets. Have you submitted this as a vscode issue? It seems that they could have their emmet processing run before add-ons/extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants