You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tabstops are not working properly when using snippets with delimiters. For example, if I have something of the kind
snippet _ "subscript" iA
_{$1}$0
endsnippet
it should first expand like {|} (here I'm using | to denote the cursor place) and then go to the second tabstop, like {}|. But for some reason, sometimes, even after pressing the next tabstop trigger (which I've set to jk) the cursor just blinks and stays right before the end of the delimiter (for example, after A_{1} it would stay like A_{1|} instead of A_{1}|).
When I say "sometimes" I mean it. This behavior triggers for some reason and after that all the snippets with delimiters stop working properly. And then it randomly starts working fine again. I can't get what triggers the behavior though.
Furthermore, it apparently is not bounded to happen just with {}. Something of the kind
snippet mk "inline math" wA
\$ $1 \$$0
endsnippet
is also not working properly.
Does someone have any idea about what's happening?
The text was updated successfully, but these errors were encountered:
Tabstops are not working properly when using snippets with delimiters. For example, if I have something of the kind
it should first expand like {|} (here I'm using | to denote the cursor place) and then go to the second tabstop, like {}|. But for some reason, sometimes, even after pressing the next tabstop trigger (which I've set to jk) the cursor just blinks and stays right before the end of the delimiter (for example, after A_{1} it would stay like A_{1|} instead of A_{1}|).
When I say "sometimes" I mean it. This behavior triggers for some reason and after that all the snippets with delimiters stop working properly. And then it randomly starts working fine again. I can't get what triggers the behavior though.
Furthermore, it apparently is not bounded to happen just with {}. Something of the kind
is also not working properly.
Does someone have any idea about what's happening?
The text was updated successfully, but these errors were encountered: