html-snippets icon indicating copy to clipboard operation
html-snippets copied to clipboard

Emmet expansion seems to be interfering with this extension

Open macintacos opened this issue 8 years ago • 5 comments

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.

macintacos avatar Mar 07 '17 16:03 macintacos

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

abusaidm avatar Mar 12 '17 11:03 abusaidm

@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.

macintacos avatar Mar 12 '17 17:03 macintacos

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.

smoses2 avatar May 10 '17 17:05 smoses2

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

abusaidm avatar May 11 '17 08:05 abusaidm

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.

smoses2 avatar May 11 '17 11:05 smoses2