I noticed a weird behavior recently when I changed the keyword length from 1 to 4. First let me give the steps to reproduce:
Set ultisnips keyword length from 1 to some high number that doesn't cause the completion menu to open.
Open a file that has snippets defined.
Trigger a snippet as defined by vim.g.ultisnipsexpandtrigger.
Try to jump to the next tabstop with tab. The tab key doesn't do anything.
Now, go into insert mode and try to jump to the next tabstop. Instead, the function call gets printed.
Here's a video showing the "bug". In the first part, I show that everything works fine when the snippet is triggered after the completion menu has opened. In the second part, I set the keyword length to 4, trigger the plugin, and then try to jump to the next tabstop. It doesn't work.
I noticed a weird behavior recently when I changed the keyword length from 1 to 4. First let me give the steps to reproduce:
vim.g.ultisnipsexpandtrigger
.tab
. The tab key doesn't do anything.Here's a video showing the "bug". In the first part, I show that everything works fine when the snippet is triggered after the completion menu has opened. In the second part, I set the keyword length to 4, trigger the plugin, and then try to jump to the next tabstop. It doesn't work.
https://user-images.githubusercontent.com/17733465/166337915-512557db-ed2b-46e5-91f6-f6858e35aba1.mp4
Here's a minimal setup.