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
{{ message }}
This repository has been archived by the owner on Jul 27, 2018. It is now read-only.
So I've followed the instructions here to setup C-U to trigger the completion menu or expand the UltiSnips trigger.
Most of the time it works as expected, but there's something I don't know how to solve: pressing C-U to trigger the pop-up in the middle of the line yields no results, but if I do it at the beginning of the line it works perfectly.
Just as a hunch, it might have to do with the snippet option itself (see here or :h UltiSnips-snippet-options).
Am Ultisnip snippet can be configured to only expand at the beginning of a line, maybe you have the b option set?
@seb-mueller Not really. My :aut snippet, for example, can be expanded anywhere on the line and doesn't show up if there's a space and I invoke C-u. After I type a few letters the completion menu will pop-up, no problem, but if I trigger it manually it only works at the beginning of the line.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So I've followed the instructions here to setup C-U to trigger the completion menu or expand the UltiSnips trigger.
Most of the time it works as expected, but there's something I don't know how to solve: pressing C-U to trigger the pop-up in the middle of the line yields no results, but if I do it at the beginning of the line it works perfectly.
Here's a demo of the problem:
Here's my NCM/UltiSnips config:
What am I doing wrong?
Thanks!
The text was updated successfully, but these errors were encountered: