Expand conflicts with Emmet

[tobalsan]

Hi,

since last update where you replaced blockb with block., ifb with if. for twig multiline blocks, if one has Emmet extension installed, there is a conflict between both plugins in text expansion, and Emmet takes priority, which makes block. expand to <block class=""></block>.

[or3lie]

Hello,
+1, it's annoying !
Somebody knows if it's possible to disable some emmet's snippets cause I never use the emmet's block and I would prefer to use the twig's snippet for block...
If no way, I think I'm going to update twig's snippets with tblock or something like that

[uhnomoli]

Hrm, that is rather annoying :{ Any suggestions for the trigger syntax for multi-lined versions of snippets? I wasn't very fond of the trailing b, hence why I changed it to the trailing .. Locally I used repeating the last letter (e.g., blockk, iff, etc.) though I'm not sure how I feel about that either.

[or3lie]

I think the same character each time is better.
Instead of a point you can choose a letter and put it at the end of the trigger.
Or maybe another character like two points, can it work ? exp : block:, if:...

[tobalsan]

+1
i like the colon solution block:, if:, Just tested it right now, no weird text expansion occuring on my side.

[or3lie]

Hi @Anomareh ! What do you think about the colon solution ?

[diegocastro]

+1 for the colon.

[tobalsan]

yeah, it would be really cool, but looks like @Anomareh is very busy lately :P

[diegocastro]

@Anomareh if you're busy I could make the changes. It's something that is annoying me to no end.