High priority text fragment

Question

I made my own snippet with a Tab trigger that inserts a large block of comments into the CSS file when starting with the keyword comment. After using it for a while, and it works fine, I installed the Emmet plugin, which inserts some kind of native code when starting Tab with any arbitrary word or combination of characters.

So now what happens is that the Emmet plugin overrides my fragment, and instead of getting my big block of comments when I type in the “comment” and press Tab, I get comment: ;it because Emmet assumes that I want to write a CSS property with the name comment.

(which doesn't even make sense, because I'm not in the block {}, but that's not the point)

My question is: how can I get my own fragment for execution with a "higher priority", so if there is a fragment with the current Tab trigger, the Emmet plugin will be ignored?

Answer 1

Try refusing tab completion: https://github.com/sergeche/emmet-sublime/issues/9

A simple workaround is to change the trigger of your fragment to mycommentor commmentor some other unforgettable but unique trigger to eliminate the entire conflict problem.